Adopting a more robust file path -> file URL conversion

The code shared in this StackOverflow answer has been granted an MIT license by the author: https://stackoverflow.com/a/35734486

Perhaps we should consider adopting it? Otherwise we're going to keep seeing edge cases (e.g. #8383)

Start by reviewing the linked Stack Overflow answer and issue #8383 to understand the file path-to-file URL edge cases described. Compare those references with the current conversion behavior; done means the project has a decided approach that addresses the reported edge cases.

Written by the indexing model from the issue text.