[fix] Add support for handling remote file URIs.

[Carpe-Wang]

Summary

This PR adds support for handling remote file URIs within the project. It addresses the issue where the system could not correctly process URIs that point to remote files.

Changes

• Implemented functionality to download remote files specified by file: URIs.
• Added unit tests to verify the correctness of this new feature.

Issue Link

Fixes #616

[bioball]

Hey Carpe, thanks for the PR!

I don't know if this is the right solution to the problem. As far as I can tell, there is no agreed upon protocol when opening files with a remote hostname.

• Windows machines will use SMB to open the file
• Safari on macOS will strip the hostname entirely and try to open the file from the local machine
• Java's URL#openConnection() will use FTP
• I can't find any examples of using HTTP to fetch the file

Without a protocol here, I think some valid choices are:

1. Explicitly don't support, and instead throw an error
2. Support on Windows only
3. Follow Java's lead and use FTP

I'm kind of leaning towards option 1 because it's the least amount of commitment and allows us to address this if the need arises later.

Curious what @holzensp and @stackoverflow think

[Carpe-Wang]

@bioball Hi bioball, I got your idea, If both of them also suggest modifying it to directly throw an exception, I will submit a new commit to implement this.

[stackoverflow]

Agree that throwing an error seems like the best solution, as there's no consensus on how to handle host names in files.

[holzensp]

I would have expected NFS on Linux/Solaris/FreeBSD/etc. Agreed; randomly guessing protocols to start hammering seems risky, at best. Exception would be the way to go.

[Carpe-Wang]

@bioball hi bioball, I change to throw the exception directly. Can you help me to ensure satisfying the requirement?