Fix line endings in Unicode diretion override tests

[cameel]

One of the tests added in #10326 has Windows line endings. We probably have some line-ending conversion that kicks in only on non-CRLF platforms because the source locations in error messages end up being different on Windows because of this.

Details

See this failed run or t_win:

ASSERTION FAILURE:
- file   : boostTest.cpp
- line   : 125
- message: Test expectation mismatch.
Expected result:
  ParserError 8936: (128-139): Mismatching directional override markers in comment or string literal.
Obtained result:
  ParserError 8936: (124-135): Mismatching directional override markers in comment or string literal.

[mijovic]

Great, let's see if windows is fine now

[axic]

We probably have some line-ending conversion that kicks in only on non-CRLF platforms because the source locations in error messages end up being different on Windows because of this.

Well, should that be the case really?

[cameel]

Depends. That's pretty typical behavior in Python for example. I'm not sure if boost in C++ adds some conversion when you read a file in text mode. Might be worth investigating. Also, do we have any tests for different line endings?

[chriseth]

The problem might also be related to git instead of C++ - the checkout routine on windows introduces different line breaks for text files.

[cameel]

But does it do it automatically? @axic says we don't have anything like this set up on purpose at least:

git has this feature to control line-ending conversion, but I don't think we have it set up

[axic]

Some details about the git feature: https://stackoverflow.com/questions/21822650/disable-git-eol-conversions

Also, do we have any tests for different line endings?

I don't think so. Well we do have scanner tests to make sure they are parsed correctly, but no tests for the error reporter.