[Python] TypeSpec migration for azure-mgmt-consumption

[msyyc]

TypeSpec migration for azure-mgmt-consumption

TypeSpec folder: specification/consumption/resource-manager/Microsoft.Consumption/Consumption

Pre-migration swagger source: specification/consumption/resource-manager@606c9fe7

Swagger API version: 2024-08-01 (default tag: package-2024-08)

Generated with apiVersion: 2024-08-01 (matched from swagger default tag)

Classification summary

All breaking changes were classified as ACCEPT per the breaking changes guide. No client.tsp mitigations were required, so no spec PR was created.

Category	Rule	Count	Examples
Multi-level flattening (properties re-introduced)	11	~100 instance-variable removals across 11 models	EventSummary, LotSummary, ReservationTransaction, ModernReservationRecommendation, LegacyReservationRecommendation, ManagementGroupAggregatedCostResult, OperationStatus, PriceSheetResult, ReservationRecommendationDetailsModel, TagsResult
Base-method name conflict	12	1	BudgetComparisonExpression.values → values_property
Pageable models removed	8	2	Events, Lots
Unreferenced / flattening side-effect models	7 / 11	6	DownloadProperties, ErrorDetails, ErrorResponseAutoGenerated, LegacyReservationTransaction, ReservationTransactionResource, ResourceAttributes
Common types upgrade (etag/tags on base resources)	6	3	Resource.etag, Resource.tags, ProxyResource.e_tag
Parameters changed to keyword-only	9	~30	ChargesOperations.list, EventsOperations.list_by_billing_profile, MarketplacesOperations.list, PriceSheetOperations.get*, ReservationRecommendationDetailsOperations.get, ReservationTransactionsOperations.list, ReservationsDetailsOperations.list, ReservationsSummariesOperations.list*, UsageDetailsOperations.list

Accepted breaking changes that will remain

All entries listed under Breaking Changes in the latest CHANGELOG.md section are accepted as-is. No mitigations applied.

Spec mitigation PR

None — no breaking changes required @@clientName or @@override decorators.