Normalize iCal line endings to CRLF

[sentry]

Fixes CALENDARPROXY-1. The issue was that: golang-ical's Serialize() uses LF instead of CRLF, causing Content-Length mismatch and client-side connection closure.

• Normalize line endings in serialized iCal data to CRLF (\r\n).
• Ensure compliance with RFC 5545 for calendar data.
• Prevent double carriage returns by first replacing existing CRLF with LF, then all LF with CRLF.

This fix was generated by Seer in Sentry, triggered by kordianbruck. 👁️ Run ID: 1153191

Not quite right? Click here to continue debugging with Seer.

[Copilot]

Pull request overview

This PR addresses CALENDARPROXY-1 by ensuring serialized iCalendar output uses CRLF (\r\n) line endings (per RFC 5545), avoiding downstream Content-Length mismatches and client disconnects.

Changes:

• Normalize golang-ical serialized output from LF to CRLF.
• Avoid double-CR issues by converting existing CRLF to LF before converting all LF to CRLF.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.