Exchange metadata between Windows & Unix complicated because of EOL

[JaroslavTulach]

While investigating so called "legit failure" in the CI Windows run I am concluding there is a problem in parsing META-DATA - there is no way to parse the same file on Windows and on other systems. To reproduce:

$ git checkout 958ac95
$ sbt runEngineDistribution --run test/Tests/src/Semantic/Instrumentor_Spec.enso

works on Linux, Mac, but fails on Windows. With a following Convert.java program:

import java.io.File;
import java.io.FileWriter;
import java.nio.file.Files;
import java.util.stream.Collectors;

public final class Convert {
    private Convert() {
    }

    public static void main(String... args) throws Exception {
        var nl = switch (args[1]) {
            case "crlf" -> "\r\n";
            case "lfcr" -> "\n\r";
            case "cr" -> "\n";
            case "lf" -> "\r";
            default -> throw new IllegalArgumentException("Specify: cr, lf or crlf");
        };
        var f = new File(args[0]).toPath();
        var txt = Files.readAllLines(f).stream().collect(Collectors.joining(nl));
        try (var w = new FileWriter(f.toFile())) {
            w.write(txt);
        }
    }
}

I can fix the problem on Windows, by running:

$ java Convert.java Instrumentor_Spec.enso "cr"

but then the file becomes unparsable on Linux & Mac. E.g. users sharing their files between windows and other system must loose their positions of widgets and visualizations as the parsing of META-DATA sections is too fragile - also reported as

• Compress enormous metadata section by 50% while making it friendlier #7989

and cannot handle parsing the same file on different systems.

[JaroslavTulach]

No direct end user problem so far. Nobody seems to care.