[TypeSpec] Add 2025-09-01 API version for Release Planner Test Product SDK generation

[Copilot]

This PR adds the 2025-09-01 API version to the Contoso.WidgetManager TypeSpec specification to support SDK generation for the Release Planner Test Product.

Changes Made

• Added v2025_09_01: "2025-09-01" to the Versions enum in /specification/contosowidgetmanager/Contoso.WidgetManager/main.tsp
• Updated the version to use @useDependency(Azure.Core.Versions.v1_0_Preview_2) for compatibility
• Validated TypeSpec compilation and generated OpenAPI specification

SDK Generation Results

Successfully generated SDK pull requests for all requested languages:

• JavaScript: [AutoPR @azure-rest-contoso-widgetmanager]-generated-from-SDK Generation - JS-5208486 azure-sdk-for-js#35541
  • Package: @azure-rest/contoso-widgetmanager
• Python: [AutoPR azure-contoso-widgetmanager]-generated-from-SDK Generation - Python-5208494 azure-sdk-for-python#42476
  • Package: azure-contoso-widgetmanager
• Go: [AutoPR sdk-contosowidget/azmanager]-generated-from-SDK Generation - Go-5208497 azure-sdk-for-go#25074
  • Package: github.com/Azure/azure-sdk-for-go/sdk/contosowidget/azmanager

All SDK details have been updated in release plan work item 28402 and linked to release plan 1485.

Testing

• TypeSpec compiles successfully with npx tsp compile .
• Generated OpenAPI specification at data-plane/Azure.Contoso.WidgetManager/stable/2025-09-01/widgets.json
• All SDK generation pipelines completed successfully

This is for testing purposes as indicated in the issue - SDKs are generated but not released.

Fixes #36615.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.