Fix line separator issues

[rnett]

Simple fix for #1884 and #1883, just replaces CRLF line separators with LF before markdown parsing. Ideally this should be fixed in the parser, but this works for now.

Also adds a test for this.

For GitHub:
Fixes #1883
Fixes #1884

[rnett]

Tests are failing because they were in the wrong spot, parseModuleAndPackageDocFragment does not use the markdown parser. parseModuleAndPackageDocFragment supports CRLF fine, but leaves them in the output. Is that intentional/a good idea, or should I switch those to LF as well (it won't line up with the markdown parser unless I do)?

[MarcinAman]

I have a bad feeling about that. What would happen if somebody would add \r\n in their documentation? Or any other escaped version of those characters?

[rnett]

I assume (unless you're doing some kind of preprocessing somewhere else) that they won't be unescaped, i.e. a "\n" in the markdown document will be parsed as ['\', 'n'] i.e. "\\n", not ['\n']. I'll add this to the tests.