Use absolute_path instead of fs::canonicalize

[topecongiro]

This PR is a successor of #3590.

[calebcartwright]

👍

[topecongiro]

I am still not sure this will work in all cases, but I will merge this for now.

[rivy]

@topecongiro , this will likely fail for deep paths even on later version Windows 10 installations. The removal of the MAX_PATH (~260 characters) limitation is opt-in and has to have a registry value set (see https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later). That's an impossible bar to expect from any significant user population. It can't really be counted on at all.

However, there is an available solution... extended-paths. Extended-paths (marked by a leading \\?\ prefix) can be used with versions of the windows API back to at least Windows 7. If the path length is greater than (or even close to) MAX_PATH, it should be converted to an extended-path by converting it to an absolute path, converting all forward slashes to backslashes, and prefixing it with \\?\.

I referenced the needed solution for this in the original issue/PR.

This type of path construction can even be used to access windows wierdo reserved paths like NUL and CON.

Please see the dunce crate which does a very good job in navigating these weird MS path waters.

[topecongiro]

@rivy Hmm, I will take a look again, but the dance crate looks promising. We might as well use it. Thank you for your information