Be more lenient on line ending character

**Is your feature request related to a problem? Please describe.**

I did a RegEx search and replace in Visual Studio and as usual forgot whether \r or \n is the magic (and the order generally eludes me as well, so the Windows \r\n is also a challenge.

Anyway, that led to me inserting \r instead of \n in my code.

The result was a bunch of very weird offside and other errors. It seemed the error might have been related to how many of them I had in the code when I did a repro (one vs many). The line/column reported was not where the \r actually was.

**Describe the solution you'd like**

Either of:

* Assume \r means line ending. There may be downsides of this.
* If \r is encountered, give at least a warning that the compiler is surprised and making assumptions, with the correct location.

**Describe alternatives you've considered**

None really. I made a mistake, so not making mistakes is always good. But fixing this would lower the waste when someone makes this particular mistake.

**Additional context**

If the issue is about:
_Not sure if this is compiler or parser. As a side note, can we change the following part of the template:_

* improving a compiler error message, please mention "related: #1103"
* improving/adjusting the parser, please mention "related: #11481"

**Impact**

The impact was fairly low. I did not have a disruption between when I did the replace and discovered the problem. Could have definitely been quite bad had their I not thought back to the previous action as this is invisible.