Update deployment version APIs definitions

[ZianWang02]

ARM (Control Plane) API Specification Update Pull Request

[!TIP] Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• [ ] New resource provider.
• [ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• [x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• [ ] Update existing version to fix OpenAPI spec quality issues in S360.
• [ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• [ ] Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood and followed the instructions by checking all the boxes:

• [x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• [x] I have reviewed following Resource Provider guidelines, including ARM resource provider contract and REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table in the `Generated ApiView` comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the [suppressions guide](https://aka.ms/azsdk/pr-suppressions) to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run. This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app[bot]]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
  To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
  When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
  Automation should then add WaitForARMFeedback label.
  ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

[openapi-pipeline-app[bot]]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/cdn/armcdn	https://apiview.dev/Assemblies/Review/5e345519a8864b018f9aae9fb7ba934c?revisionId=b8e431e885344e38942b56bfd697d052
JavaScript	@azure/arm-cdn	https://apiview.dev/Assemblies/Review/d03c7f4c0d164abd85030a921f78f9ad?revisionId=25ab748721de46b7ad8a7f656a053020
Java	azure-resourcemanager-cdn-generated	https://apiview.dev/Assemblies/Review/a857fa609d3c43b09808544a49c0693b?revisionId=eb5354d7244144ff9931807d5bb83d87
Python	azure-mgmt-cdn	https://apiview.dev/Assemblies/Review/554f619b5bce4305ab34ed93bfc66da9?revisionId=70101e12d5ce4592a014d888090f74d4

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.Cdn

[ZianWang02]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).

[ZianWang02]

Hi ARM DRI, our deployment version feature is controlled by the feature flag and not used by any customer yet. We would like to update the swagger for the 2024-06-01-preview version to update the definition. Can we add the tag "Versioning-Approved-BugFix" to bypass the breaking change check? Here is the changes for this PR:

1. Update the property of the deploymentVersion.properties.stages.production to an enum value.
2. Update the property of the deploymentVersion.properties.stages.preview to an enum value.
3. Remove the Microsoft.Cdn/profiles/securitypolicies from the enum DeploymentVersionChange because it is not supported.

[ms-bogdan-rotaru]

@ZianWang02 The breaking change label has to be added by the Breaking Change Review board - aka.ms/brch Please get this approval first and get put the PR back in the queue for API review.

[ZianWang02]

Hi @ms-bogdan-rotaru, is it possible for us to bypass the Breaking Change review because the API related to the Microsoft.Cdn/profiles/deploymentversions is controlled by the feature flag and not opened to any customer yet?

[ms-bogdan-rotaru]

Please follow the instructions and details provided at https://aka.ms/brch. Only the members of Breaking Change approval board can take these decisions.