Fix: Add support for abfss protocol

[jslorrma]

Description

This pull request addresses the issue where defining a UPath with the Azure protocol "abfss" causes a ValueError:

File .../lib/python3.11/site-packages/upath/implementations/cloud.py:104, in AzurePath.__init__(self, protocol, *args, **storage_options)
    102 print(self.drive, len(self.parts))
    103 if not self.drive and len(self.parts) > 1:
--> 104     raise ValueError("non key-like path provided (bucket/container missing)")

ValueError: non key-like path provided (bucket/container missing)

This fixes #310

Fix

This pull request adds "abfss" to the WrappedFileSystemFlavour.protocol_config["netloc_is_anchor"] list to ensure that the splitdrive method correctly handles paths with the "abfss" protocol.

[ap--]

Thank you for your contribution @jslorrma ❤️

Some additional information and links:

AzureBlobFileSystem protocol registration seems to be a bit convoluted. Ultimately all three az, abfs, and abfss are registered.

• The AzureBlobFileSystem class only claims abfs https://github.com/fsspec/adlfs/blob/4cf4c8535ab7ba88a586bd0fa5f5e9db484f5b6e/adlfs/spec.py#L240
• but its _strip_protocol method handles all three: https://github.com/fsspec/adlfs/blob/4cf4c8535ab7ba88a586bd0fa5f5e9db484f5b6e/adlfs/spec.py#L377
• fsspec.registry:known_filesystems registers abfs https://github.com/fsspec/filesystem_spec/blob/ac830a007a16ccceaf7b0eef5c7e13d57840e6c6/fsspec/registry.py#L63-L66
• as well as az https://github.com/fsspec/filesystem_spec/blob/ac830a007a16ccceaf7b0eef5c7e13d57840e6c6/fsspec/registry.py#L67-L70
• abfss is registered via an entrypoint: https://github.com/fsspec/adlfs/blob/4cf4c8535ab7ba88a586bd0fa5f5e9db484f5b6e/pyproject.toml#L45-L46