isolate changes for meshupgradperofile and meshrevisionprofile resour…

[SanyaKochhar]

ARM (Control Plane) API Specification Update Pull Request

Purpose of this PR

This PR is a subset of changes made in #24453. The purpose is to get ARM API review as a prerequisite for new resource types being introduced. Once it has been approved, it does not need to be merged since it will be part of the AKS 2023-06-02preview changes PR from Fuming's branch (the base branch for this PR).

Since these changes already exist in the base branch, the examples are not showing up in the diff. They can be found here: https://github.com/Azure/azure-rest-api-specs/pull/24453/files#diff-8c56973c856d65b77b194b0f7326c12bfb280a3fe8b5574d29233a22ddf21bd4

What's the purpose of this PR? Check all that apply. This is mandatory!

• New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
• 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 swagger quality issues in S360.
• 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:

• I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
• I commit to follow the Breaking Change Policy.
• 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 request review from an ARM API Review board.

ARM API changes review

• If you want for the ARM team to review this PR, you must add the ARMReview label.
• The automation may automatically add the ARMReview label, if appropriate.
  If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review

If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.

Getting help

• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For additional help, see https://aka.ms/azsdk/support/spectools.

[openapi-pipeline-app]

Swagger pipeline can not start as the pull request has merge conflicts.

[openapi-workflow-bot]

Hi, @SanyaKochhar! Thank you for your pull request. To help get your PR merged:
- Ensure you reviewed the checklists in the PR description. - Know that PR assignee is the person auto-assigned and responsible for your current PR review and approval. - 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.

[openapi-pipeline-app]

Swagger pipeline can not start as the pull request has merge conflicts.

[openapi-pipeline-app]

Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment.

[openapi-pipeline-app]

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️SwaggerAPIView succeeded [Detail] [Expand]

️️✔️CadlAPIView succeeded [Detail] [Expand]

️️✔️TypeSpecAPIView succeeded [Detail] [Expand]

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️CadlValidation succeeded [Detail] [Expand]

Validation passes for CadlValidation.

️️✔️TypeSpec Validation succeeded [Detail] [Expand]

Validation passes for TypeSpec Validation.

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

Breaking Changes Tracking

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[SanyaKochhar]

Closing in favor of PR in another repo that shows the diff more clearly