[WIP][arm-common-types] - closing gaps & validation with compare tool

[AlitzelMendez]

common-types still have some differences, we want to remove as much differences as possible so we can call common-types "ready"

I still have some questions that I need to follow up:

1. visibility versioning - The visibility change across versions, do we have a way to handle this?
2. parameters section - In some places the parameters section is missing, what role the parameters section plays on the swagger?
3. @@OpenAPI.extension versioning - There are some extensions that change across versions like x-ms-null
4. x-ms-arm-id-details - Which is the role? in some places on the original swagger it doesn't exist, but we added it

[azure-sdk]

All changed packages have been documented.

• ✅ @azure-tools/typespec-azure-resource-manager

Show changes

@azure-tools/typespec-azure-resource-manager - feature ✏️

common-types consistency with original swagger

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	📚 Next docs