Normalize slashes in paths in TASTy binaries

[abgruszecki]

[test_windows_full]

[abgruszecki]

@liufengyun Asking since you were involved with similar PRs, also involving Windows. It seems like cmdTests are not run on Windows. This PR ensures that we always use / to separate path elements in TASTy binary files, can you think of any way of testing that on Windows?

[abgruszecki]

@bishabosha since you worked around TASTy reader, are there any tests for it that get ran on Windows?

[bishabosha]

@abgruszecki One way i normalised paths was in ExtractSemanticDB where the path is converted to javas URI

[abgruszecki]

@nicolasstucki Should we mention somewhere that the paths in tasty binaries always use forward slashes?

[nicolasstucki]

Documentation for this is a good idea.

• Can we add it to the TastyFromat?
• We should also add it in the reflection API
• It would be good to repeat it in the method that normalizes the path to make sure the next person that modifies it knows about this.

[liufengyun]

@liufengyun Asking since you were involved with similar PRs, also involving Windows. It seems like cmdTests are not run on Windows. This PR ensures that we always use / to separate path elements in TASTy binary files, can you think of any way of testing that on Windows?

Yes, cmdTests only run on Linux machines. Currently, we don't have scripts that run on Windows. A possibility would be to create a macro test, and print the relative path of a symbol.

[abgruszecki]

@nicolasstucki where should we modify TastyFormat?

[abgruszecki]

And yes, I'll also modify the Quotes API.