fsspec path handling

Proposed as fix for #3201. Some filesystems need the scheme as part of the path,
while others don't. FsspecStore.from_url() throws an exception if the scheme is
left in the path, for any filesystem except http and https. However, the swift fs
also needs the scheme in the path. This commit removes the exception, rather than
adding more special cases.

Author: fjansson

src/zarr/storage/_fsspec.py

@@ -139,10 +139,6 @@ def __init__(
                 f"fs ({fs}) was not created with `asynchronous=True`, this may lead to surprising behavior",
                 stacklevel=2,
             )
-        if "://" in path and not path.startswith("http"):
-            # `not path.startswith("http")` is a special case for the http filesystem (¯\_(ツ)_/¯)
-            scheme, _ = path.split("://", maxsplit=1)
-            raise ValueError(f"path argument to FsspecStore must not include scheme ({scheme}://)")
 
     @classmethod
     def from_upath(
@@ -247,12 +243,6 @@ def from_url(
         if not fs.async_impl:
             fs = _make_async(fs)
 
-        # fsspec is not consistent about removing the scheme from the path, so check and strip it here
-        # https://github.com/fsspec/filesystem_spec/issues/1722
-        if "://" in path and not path.startswith("http"):
-            # `not path.startswith("http")` is a special case for the http filesystem (¯\_(ツ)_/¯)
-            path = fs._strip_protocol(path)
-
         return cls(fs=fs, path=path, read_only=read_only, allowed_exceptions=allowed_exceptions)
 
     def with_read_only(self, read_only: bool = False) -> FsspecStore: