Update cmdlet to support arc gateway

[xw-zhang24]

Description

The PR aims to add support to enable arc gateway feature on ConnectedKubernetes cmdlet during resource creation and update. Due to limit of current swagger design on PATCH, we introduced Set-AzConnectedKubernetes to allow modification on arc gateway feature on existing resources following the best practice. Design and discussion are available in this doc

We suggest to put following bullets in changelog:

• Added support for arc gateway feature in cmdlet New-AzConnectedKubernetes
• Added Set-AzConnectedKubernetes cmdlet to support updateing arc gateway features on existing resource

We are waiting for dependency services to be released first in late September, so the targeting release for now will be October.

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[xw-zhang24]

@msJinLei and other reviewers,

The pipeline currently fails at build due to autorest failure on Storage, which is totally unrelated to the PR change. In fact, the failing module, along with other module, only started to be included at build from commit which adds analysis exception, I wonder if that triggers all modules to build. Regarding the failure, I'm not familiar with the failing module itself, but I've tried to build the it locally and it failed with autorest 4.0 but passed with autorest 3.0. Is there anyway to build without unrelated module, or configure some modules to build on different autorest version? If these are not options, how to make the pipeline happy again? Thanks,

[msJinLei]

Lei is following up the build issue

[msJinLei]

Please provide the change log for your PR

[msJinLei]

Please use singular name

[xw-zhang24]

@msJinLei We kept the plural form in the name to maintain consistency with the other commands in this module:

Get-AzConnectedKubernetes
New-AzConnectedKubernetes
Remove-AzConnectedKubernetes
Update-AzConnectedKubernetes

We've also put an exception to suppress the analysis check for plural in this commit

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

[xw-zhang24]

Please provide the change log for your PR

@msJinLei Thanks for your review and comments.

As the change is autorest based, we have put changelog in PR description as required, but happy to duplicate below.

We suggest to put following bullets in changelog:

Version 0.11.0
- Added support for arc gateway feature in cmdlet New-AzConnectedKubernetes
- Added Set-AzConnectedKubernetes cmdlet to support updateing arc gateway features on existing resource