[Az.EventGrid] Add partner features from 2022-06-15 API

[Brandon411]

Description

Design review: https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/1252

Adding new cmdlets:

• Get-AzEventGridPartnerRegistration
• Get-AzEventGridPartnerConfiguration
• Get-AzEventGridVerifiedPartner
• Get-AzEventGridPartnerNamespace
• Get-AzEventGridChannel
• Get-AzEventGridPartnerNamespaceKey
• Get-AzEventGridPartnerTopic
• Get-AzEventGridPartnerTopicEventSubscription
• New-AzEventGridPartnerRegistration
• New-AzEventGridPartnerConfiguration
• New-AzEventGridPartnerNamespace
• New-AzEventGridPartnerTopic
• New-AzEventGridChannel
• New-AzEventGridPartnerTopicEventSubscription
• Update-AzEventGridPartnerConfiguration
• Update-AzEventGridChannel
• Update-AzEventGridPartnerTopic
• Update-AzEventGridPartnerTopicEventSubscription
• Remove-AzEventGridPartnerRegistration
• Remove-AzEventGridPartnerConfiguration
• Remove-AzEventGridPartnerNamespace
• Remove-AzEventGridChannel
• Remove-AzEventGridPartnerTopic
• Remove-AzEventGridPartnerTopicEventSubscription
• Grant-AzEventGridPartnerConfiguration
• Enable-AzEventGridPartnerTopic
• Revoke-AzEventGridPartnerConfiguration
• New-AzEventGridPartnerNamespaceKey

Checklist

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

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at 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. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[wyunchi-ms]

Do you want to go to this release or next release? If this release, please retarget to release branch release-2022-10-12

[wyunchi-ms]

No need to update the version manually. Our tools will do it when build the release.

[Brandon411]

Removed manual version increment

[wyunchi-ms]

1. No need to update the version manually. Our tools will do it when build the release.
2. Just add changelog to section Upcoming Release

[Brandon411]

Removed manual version increment and added changelog to the Upcoming Release section

[Brandon411]

Do you want to go to this release or next release? If this release, please retarget to release branch release-2022-10-12

When is the next release? I don't think we will make the 10/12/2022 date.

[VeryEarly]

Do you want to go to this release or next release? If this release, please retarget to release branch release-2022-10-12

When is the next release? I don't think we will make the 10/12/2022 date.

it will be 2022-11-01

[VeryEarly]

please fix examples: https://dev.azure.com/azclitools/public/_build/results?buildId=8328&view=logs&jobId=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&j=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&t=e8689ae8-b216-55f7-b207-4831f84ff98a

and tests: https://dev.azure.com/azclitools/public/_build/results?buildId=8328&view=logs&jobId=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&j=b17395f6-68a3-5682-0476-d3f6f1043109&t=67f633ab-4360-5839-af42-f446e0c847f0

[Brandon411]

please fix examples: https://dev.azure.com/azclitools/public/_build/results?buildId=8328&view=logs&jobId=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&j=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&t=e8689ae8-b216-55f7-b207-4831f84ff98a

and tests: https://dev.azure.com/azclitools/public/_build/results?buildId=8328&view=logs&jobId=e1b7b984-9f58-529f-7c5a-f15f8e35cfa6&j=b17395f6-68a3-5682-0476-d3f6f1043109&t=67f633ab-4360-5839-af42-f446e0c847f0

Fixed

[VeryEarly]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).