[StorageSync] Bump API version to 2025-12-01

[JunKai-v]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

• az storagesync check-name-availability
• az storagesync private-endpoint-connection list
• az storagesync sync-group cloud-endpoint trigger-change-detection

Partially addresses Azure/azure-cli#33971.

Changes

• Regenerated the 3 AAZ commands above with aaz-dev against Microsoft.StorageSync stable/2025-12-01 (spec tag package-2025-12), up from 2022-06-01.
  • check-name-availability: error format follows the new spec (ODataV4Format).
  • private-endpoint-connection list: response schema adds nextLink and read-only properties.groupIds.
  • trigger-change-detection: LRO now uses final-state-via: location, per the 2025-12-01 spec.
• azext_metadata.json: minCliCoreVersion 2.55.0 -> 2.75.0 (set by the code generator).
• Extension version 1.0.1 -> 1.1.0, with a HISTORY.rst entry.

Not in this PR (scope still being confirmed on the issue)

• The remaining commands (storagesync create/show/list/delete, sync-group, cloud-endpoint create/show/list/delete, server-endpoint, registered-server) still use the vendored SDK at 2019-06-01.
• New in 2025-12-01 and not yet exposed: CloudEndpoints_Update (a new cloud-endpoint update command) and changeEnumerationIntervalDays.
• Matching AAZ command models for Azure/aaz are prepared locally; that PR is not opened yet.

Testing

• azdev style storagesync: Pylint PASSED, Flake8 PASSED.
• python scripts/ci/test_index.py -q: 9 tests OK (2 skipped).
• test_storagesync (playback): fails, pre-existing. It also fails on unmodified main. Its first step, az group create, was recorded with resource API 2022-09-01, but current azure-cli core sends 2024-11-01. A live re-recording is needed.
• Ad-hoc playback check of only the 3 changed commands, using their recorded calls with the api-version updated to 2025-12-01: passed. This was a local check only; it is not committed and is not a substitute for a live recording.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install azdev required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Yong Zhang (yonzhan)]

/azp run

[azure-pipelines]

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