std::fs::path::Path should probably use a ByteArray instead of a String

[yorickpeterse]

String requires its data to be valid UTF-8 and replaces invalid sequences with a replacement character. File paths in turn don't necessarily need to be valid UTF-8. As such, we should probably change the underlying storage of Path from a String to a ByteArray.

[yorickpeterse]

On second thought: using a String may not be so bad, as most Unix tools seem to assume paths are UT-8 anyway. E.g. Gnome Files shows encoding errors in file names that contain invalid UTF-8. Internally the VM uses strings for paths as well, and I'm not sure from the top of my head what we'd use there as an alternative.

[yorickpeterse]

We need to figure out the following:

1. What do different OS'/DEs do when a file path contains invalid UTF-8 sequences?
2. What do different languages use to back their path types if they have any?

Since this is something contributors can take care of, I'll add the "accepting contributions" label. The actual code changes however need to be discussed first (as in, we need the data first, then we can look at the code), so we can figure out what the impact will be. This way we can avoid somebody submitting a big PR, only for it to be rejected (e.g. because I feel the changes can be done differently/better).