fix: CRLF newline handling and error span rendering

Previously, newline detection operated per character, causing CRLF to be
treated as two separate newlines. This resulted in incorrect line numbers,
extra blank lines, and misaligned error spans on Windows inputs.

This change introduces CRLF-aware newline parsing while preserving support
for LF, CR, and Unicode newline characters.

Also fixes:
- incorrect line/column calculation for multi-line spans
- UTF-16 column alignment for multi-byte characters
- off-by-one error in multiline underline rendering
- zero-length spans not displaying a caret

Error rendering is now consistent across platforms and input encodings.

Merge after PR #257

Author: metalurgical

src/error.rs

@@ -324,7 +324,7 @@ where
 }
 
 impl<'tokens, 'src: 'tokens, I> LabelError<'tokens, I, DefaultExpected<'tokens, Token<'src>>>
-for RichError
+    for RichError
 where
     I: ValueInput<'tokens, Token = Token<'src>, Span = Span>,
 {
@@ -704,8 +704,8 @@ let x: u32 = Left(
         let error = Error::CannotParse(
             "Expected value of type `u32`, got `Either<Either<_, u32>, _>`".to_string(),
         )
-            .with_span(Span::new(41, FILE.len()))
-            .with_file(Arc::from(FILE));
+        .with_span(Span::new(41, FILE.len()))
+        .with_file(Arc::from(FILE));
         let expected = r#"
   |
 2 | let x: u32 = Left(
@@ -885,4 +885,4 @@ let x: u32 = Left(
 
         assert_eq!(&expected[1..], &error.to_string());
     }
-}
+}