[TSP Migration][authorization-12-01]TypeSpec migrated from swagger

[mcgallan]

This PR migrates your latest version (identified by the tag in your readme.md) of swagger to TypeSpec. We already tried our best to make sure the TypeSpec represents same as previous swagger. Since we lack the business knowledge, please validate this PR again to make sure it's functional equivalent as before. The local validation step is at Getting started | TypeSpec Azure

Besides, TypeSpec encourages to follow ARM guidelines. Therefore, some representations in your previous swagger will be fixed to follow these guidelines. When you see differences in your local validation, please keep this note in mind.

Please reach out to TypeSpec Discussions Channel if there is any help needed.

The following known differences were identified during the migration from Swagger to TypeSpec and are documented here for transparency:

1.x-ms-azure-rbac-permissions-required not yet supported — The x-ms-azure-rbac-permissions-required extension used in the ClassicAdmin spec cannot currently be expressed in TypeSpec. A dedicated decorator to support this extension is planned for a future update.

2.x-ms-client-flatten removed due to discriminator conflict — The @flattenProperty decorator has been removed from AccessReviewDecisionProperties.principal, AccessReviewDecisionInsight.properties, AlertIncident.properties, and AlertConfiguration.properties, as property flattening is incompatible with discriminated union types in TypeSpec.

3.Extra x-ms-identifiers on RoleAssignmentListResult — The generated output for RoleAssignmentListResult in RoleAssignment.Management includes an unintended x-ms-identifiers annotation (["roleAssignmentName", "id"]). This is a known TypeSpec emitter behavior and will be addressed.

4.x-ms-discriminator-value emitted for derived models — In the 2024-09-01-preview openapi.json, models that extend a base model decorated with @Discriminator will emit x-ms-discriminator-value in the generated Swagger. This is expected TypeSpec behavior.

5.UserType naming conflict — Two distinct UserType definitions with different content exist across the specs. To resolve the naming collision, they have been temporarily renamed to CommonUserType and UserType respectively. A long-term resolution is pending.

6.PolicyProperties loses readOnly when used as resource properties — When PolicyProperties is referenced as the properties bag of a resource model, the readOnly constraint on its fields is not preserved in the generated output. This is a known limitation and will be investigated.

[github-actions]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Comment generated by summarize-checks workflow run.

[mentat9]

@mcgallan - Please address Required CI checks that are failing (Swagger Avodado and Swagger ModelValidation).

[pshao25]

Avocado failed because of multiple API. ModelValidation failed because the original swagger doesn't have examples.