Specify azure requirements in date version

Azure publishes their packages with both date based versions and absolute versions. Currently, adlfs only specifies using the absolute version (eg. azure-core==1.28.0). This is an issue because Azure does not support some of their packages in this manner.

I created an issue with the Azure team, which they seem wholly uninterested in resolving. You can see it here

With that being the case, can we update the version requirements here to support the date based versioning system?

The biggest issue is azure-core >1.28.0 and <2.0.0. These versions are contained within packages 2023.09.01 to 2025.09.01 which can be seen here.

To be clear, it would be ideal to specify the requirements in both absolute form and date form, because some people still use the absolute form. But Azure has made it impossible to only use the absolute form, as some packages are simply only available in the date form (see the issue linked above).

However, I do not know if it is technically possible to list a parallel set of requirements in conda.

Locate adlfs's Azure dependency requirements and conda package metadata, then compare how absolute and date-based Azure versions can be expressed together. Check the existing dependency or packaging tests; done means supported Azure packages can resolve and install under both versioning forms without breaking current users.