[Python] TypeSpec migration for azure-mgmt-extendedlocation

[ChenxiJiang333]

[Python] TypeSpec migration for azure-mgmt-extendedlocation

Spec Source

Spec PR: Azure/azure-rest-api-specs#42299

Pre-migration swagger source: specification/extendedlocation/resource-manager@98a4db5d

Swagger API version: 2021-08-31-preview (default tag: package-2021-08-31-preview)

Generated with apiVersion: 2021-08-31-preview (matched from swagger default tag)

Spec Customizations Applied

• @@clientName(Microsoft.ExtendedLocation, "CustomLocations", "python") — restore original client name
• @@override(CustomLocations.update, ...) — flatten body into identity, properties, tags kwargs

Breaking Change Analysis

• 1 mitigated breaking change (client rename)
• 33 accepted breaking changes

Mitigated Breaking Change

Breaking Change	Classification	Mitigation
Client renamed from CustomLocations to CustomLocationsMgmtClient	Guide #4: Client Naming Changes	@@clientName(Microsoft.ExtendedLocation, "CustomLocations", "python")

Accepted Breaking Changes (will remain)

Guide #11 - Removal of multi-level flattened properties (handled by existing @@Legacy.flattenProperty in back-compatible.tsp):

• CustomLocationOperation: description, operation, provider, resource moved into nested display object
• PatchableCustomLocations: authentication, cluster_extension_ids, etc. moved into nested properties object
• PatchableResourceSyncRule: priority, provisioning_state, selector, target_resource_group moved into nested properties object
• CustomLocationsOperations.update: identity, tags changed to keyword-only; nested properties moved into properties param
• ResourceSyncRulesOperations.begin_update: individual parameters replaced by single parameters object

Guide #8 - Removal of Pageable Models:

• CustomLocationOperationsList removed (pageable behavior preserved via ItemPaged)

Guide #12 - Property name conflict with base model methods:

• MatchExpressionsProperties.values renamed to values_property