docs: document supported Azure file path formats

The object_store crate (apache/arrow-rs-object-store) supports a variety of Azure URL/path formats in its Azure builder. We should clearly document which formats Lance officially supports, so users know what they can pass as dataset URIs.

Here are all the variations recognized by the upstream object_store Azure builder:

Scheme-based (fsspec / Hadoop style):

• abfs[s]://<container>/<path>
• abfs[s]://<file_system>@<account_name>.dfs.core.windows.net/<path>
• abfs[s]://<file_system>@<account_name>.dfs.fabric.microsoft.com/<path>
• az://<container>/<path>
• adl://<container>/<path>

HTTPS (Azure Blob Storage):

• https://<account>.blob.core.windows.net
• https://<account>.blob.core.windows.net/<container>
• https://<account>.dfs.core.windows.net

HTTPS (Microsoft Fabric / OneLake):

• https://<account>.dfs.fabric.microsoft.com
• https://<account>.dfs.fabric.microsoft.com/<container>
• https://<account>.blob.fabric.microsoft.com
• https://<account>.blob.fabric.microsoft.com/<container>
• https://onelake.dfs.fabric.microsoft.com/<workspaceGUID>/<itemGUID>/Files/<path>
• https://onelake.dfs.fabric.microsoft.com/<workspace>/<item>.<itemtype>/<path>/<fileName>

We should:

1. Document which of these formats are officially supported and tested in Lance (Rust, Python, Java).
2. Call out any formats that are known to not work or have caveats.
3. Add examples in our documentation showing common Azure usage patterns.

Start by reviewing the object_store Azure builder and checking the listed URI variations across Lance's Rust, Python, and Java interfaces. Record which formats are supported and tested, note known failures or caveats, and add documentation examples for common Azure usage patterns; done means the supported formats and limitations are clear to users.