[tomotakatakahashi]

What are you trying to accomplish?

My product depends on Microsoft's speech-sdk-spm.

        .package(url: "https://github.com/microsoft/speech-sdk-spm", from: "1.53.0"),

When I run dependabot for my product, I get 403 errors:

error: failed downloading 'https://csspeechstorage.blob.core.windows.net/drop/1.53.0/MicrosoftCognitiveServicesSpeech-EmbeddedXCFramework-1.53.0.zip' which is required by binary target 'MicrosoftCognitiveServicesSpeechEmbedded-iOS': badResponseStatusCode(403)
error: failed downloading 'https://csspeechstorage.blob.core.windows.net/drop/1.53.0/MicrosoftCognitiveServicesSpeech-XCFramework-1.53.0.zip' which is required by binary target 'MicrosoftCognitiveServicesSpeech-iOS': badResponseStatusCode(403)
error: failed downloading 'https://csspeechstorage.blob.core.windows.net/drop/1.53.0/MicrosoftCognitiveServicesSpeech-MacOSXCFramework-1.53.0.zip' which is required by binary target 'MicrosoftCognitiveServicesSpeech-macOS': badResponseStatusCode(403)
error: fatalError

This PR should fix the 403 errors.

I couldn't find any related existing GitHub issues.

Anything you want to highlight for special attention from reviewers?

• I used an AI agent to create this PR, so I'm not very confident about this PR.
• I'm not 100% sure if Microsoft owns the host csspeechstorage.blob.core.windows.net. I suppose so because the speech-sdk-spm repository refers to it.
• The Smoke CI jobs are failing, but it seems unrelated to this PR's changes.

How will you know you've accomplished your goal?

I will know it if the dependabot job succeeds without the 403 errors.

• Error Reproduction:
  • Repository: https://github.com/tomotakatakahashi/dependabot-403-reproduction
  • Error log: https://github.com/tomotakatakahashi/dependabot-403-reproduction/actions/runs/40038173567/job/120702664848

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
  • DOCKER_DEFAULT_PLATFORM=linux/amd64 ./script/test echo $? -> 0
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
  • I added URLs to the unit tests and ran ./script/test, but I haven't tested this end-to-end manually (e.g., with curl through the proxy).
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.