Increment version for storage releases

[azure-sdk]

Increment package version after release of azure-storage-files-datalake

[antkmsft]

@microzchang, are you still planning to release Blobs and Files Shares betas?

[Jinming-Hu]

@microzchang, are you still planning to release Blobs and Files Shares betas?

No, there was something wrong with APIView tool. The changes were not approved by architects. We've missed the release date. We have to wait until next month.

[antkmsft]

@Jinming-Hu, AFAIK, the fix for the ApiView is ready, and the entire week is considered in-band release not to mention out-of-boud releases. Plus, maybe Betas are fine to go without an architect approval. But up to you.
As a release driver, it is good to know about your updated plans, I am going to unmark the corresponding release items and will merge the corresponding PR without waiting for the other releases (but if you change your mind, it will still be possible to update them, it is all flexible enough, but still I need to know about the change in plans).

[antkmsft]

Is it ok to get this merged?

Not that it is an unavoidable problem, but with the version published to vcpkg repo and our repo still having an old version number, it breaks vcpkg daily validation run (microsoft/vcpkg#17119).