Environment config files are not compatible across platforms

[glopesdev]

Currently the local environment .config file relies on OS-specific path separators to determine assembly locations and native library folders. Because of this, it is currently not possible to version .config files across platforms, e.g. Windows and Linux, since the direction of slashes is different.

A proposal was made in #1572 to resolve this by simply removing the explicit locations from the config file entirely. Unfortunately there are challenges to implementing this quickly, so it might be easier for now to simply normalize the paths to the current OS when reading, and normalize to a fixed convention when writing the config file, e.g. to linux-style for increased compatibility.

[glopesdev]

One possible edge case (or maybe not even) to consider is the CLI flag --lib which allows passing custom folders. This would still work if we normalize to forward slashes only on saving the .config file.

Better yet, we can do nothing and just assume that --lib is always called in an OS-specific setting so it is the caller's responsibility to ensure that any specified path is valid for the current OS.