__str__ now requires initialized fsspec module #198
Description
Previously (upath < 0.2.0) you could do a str(path) without the backend loading the fsspec module for a particular module. Which I think it should not. Now, in upath 0.2.0+ the fsspec strip_protocol through strip_upath_protocol gets called which tries to load the backend module.
Can we reinstate the previous behavior as eagerly loading a module for a string representation does not seem to make sense and it should honor the _protocol_dispatch flag