Bumped Azurite version to 3.33.0

[Thovenaar]

Description

Fixes the following exception when starting an Azure Storage container with .NET 9 packages installed.

"Azure.RequestFailedException: The API version 2025-01-05 is not supported by Azurite. Please upgrade Azurite to latest version and retry."

Checklist

• Is this feature complete?
  • [x] Yes. Ready to ship.
  • [ ] No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • [x] Yes
  • [ ] No
• Did you add public API?
  • [ ] Yes
  • If yes, did you have an API Review for it?
    • [ ] Yes
    • [ ] No
  • Did you add <remarks /> and <code /> elements on your triple slash comments?
    • [x] Yes
    • [ ] No
  • [ ] No
• Does the change make any security assumptions or guarantees?
  • [ ] Yes
  • If yes, have you done a threat model and had a security review?
    • [ ] Yes
    • [ ] No
  • [x] No

• Does the change require an update in our Aspire docs?

  • [ ] Yes
  • Is this introducing a breaking change?
    • [ ] Yes
    • Link to aspire-docs issue (please use this breaking-change template):
    • [ ] No
    • Link to aspire-docs issue (please use this doc-idea template):
  • [x] No

  Microsoft Reviewers: Open in CodeFlow

[eerhardt]

I'd like to understand how you got this exception better. Did you explicitly update Azure.Storage.Blobs to 12.23.0? The Aspire.Azure.Storage.Blobs package references 12.22.2, which doesn't know about 2025-01-05.

Typically we update the container version and the client integration version at the same time. Can you also update

https://github.com/dotnet/aspire/blob/109f7ddc71561ec71fd08106f2c575fb8d9d5167/Directory.Packages.props#L23-L24

as well?

[Thovenaar]

I'd like to understand how you got this exception better. Did you explicitly update Azure.Storage.Blobs to 12.23.0? The Aspire.Azure.Storage.Blobs package references 12.22.2, which doesn't know about 2025-01-05.

Typically we update the container version and the client integration version at the same time. Can you also update

https://github.com/dotnet/aspire/blob/109f7ddc71561ec71fd08106f2c575fb8d9d5167/Directory.Packages.props#L23-L24

as well?

I am not completely sure which package upgrade caused the issue, since it started happening after everything was upgraded to the latest version. However, both packages you mentioned are on the latest version on our side.

[Thovenaar]

@dotnet-policy-service agree