Cross-version breaking change when adding x-ms-enum wasn't flagged in CI

[jhendrixMSFT]

The following PR introduced a new API version for storage (control-plane).

Azure/azure-rest-api-specs#19357

In common.json, CorsRule.allowedMethods had the x-ms-enum extension added to control the name and not rely on an auto-generated one. This resulted in a different name from the previous API version which didn't have the x-ms-enum extension.

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/storage/resource-manager/Microsoft.Storage/stable/2021-09-01/common.json#L32

This was not flagged as a cross-API version breaking change when it should have been.

CC @mikekistler

[raych1]

@jianyexi , can you provide update?

[jianyexi]

already fixed