[Libba Lawrence (l0lawrence)]

Description

Integrates reusable opt-in Rust toolchain support with the native transfer extension's storage feature branch so storage live-test jobs can build their native development requirements.

• Forward opt-in Rust toolchain settings through the test stage and live-test job templates, preserving existing defaults for other services.
• Install the toolchain before native development-requirement builds and forward the required environment into cibuildwheel.
• Enable the storage tests pipeline using the same Rust feed and working directory as storage wheel builds, retaining all four default services.
• Add regression coverage for parameter forwarding, environment handling, PowerShell parsing, and storage configuration.

Targets feature/storage/native-transfer-ext, based on 01298e774616e2bffd6837c459faa71cab69b0ff. The original feature and reusable-support branches are unchanged.

Local validation:

• python -m pytest eng\tools\azure-sdk-tools\tests\test_native_build_pipeline.py eng\tools\azure-sdk-tools\tests\test_1es_proxy_trust.py -q --disable-warnings -k 'not test_cargo_feed_configuration_uses_default_cargo_home' — passed: 85 tests, 1 deselected. The unchanged deselected test is unsafe on Windows because PowerShell resolves $HOME to the actual user home and could write example Cargo configuration there.
• python -m black --check --line-length 120 eng\tools\azure-sdk-tools\tests\test_native_build_pipeline.py — passed.
• git -c core.longpaths=true diff --check — passed.

The python - storage - tests pipeline has not been queued: Azure DevOps REST redirects to sign-in and no noninteractive DevOps credential is available. Local regression results do not establish storage CI success.

No SDK regeneration or API-spec changes. No package changelog change: this PR changes pipeline infrastructure and its regression tests only.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Libba Lawrence (l0lawrence)]

/azp run python - storage - tests

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Libba Lawrence (l0lawrence)]

/azp run python - storage - tests

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).