[Feature]: Support for remote paths in `pynwb.read_nwb`

[rly]

What would you like to see added to PyNWB?

Follow up to #1974.

Add support for remote paths in pynwb.read_nwb which requires a change to NWBHDF5IO.can_read. This should be doable. We may want to change can_read to return the read h5py object so that we are creating two h5py objects - one in can_read and one in read_nwb.

Is your feature request related to a problem?

Trying to simplify how users open NWB files across backends and data sources

What solution would you like?

See above

Do you have any interest in helping implement the feature?

Yes.

Code of Conduct

• I agree to follow this project's Code of Conduct
• Have you checked the Contributing document?
• Have you ensured this change was not already requested?

[CodyCBakerPhD]

Note the original inspiration from good ol' NWB Inspector had this: https://github.com/NeurodataWithoutBorders/nwbinspector/blob/4dda364954afd1faaaf846aed8863572c39f0627/src/nwbinspector/tools/_read_nwbfile.py#L136

[CodyCBakerPhD]

SpikeInterface also has some sophisticated tooling for this: https://github.com/SpikeInterface/spikeinterface/blob/main/src/spikeinterface/extractors/nwbextractors.py#L20