Migrate Monitor from generation to main

[azure-pipelines[bot]]

Description

Migrate Monitor from generation to main The last commit of src/Monitor in generation is: commit d02682fcbf02d7e3a92e8ca41f33c8e36821dde4 Author: Jingchuan Huang [email protected] Date: Wed Oct 9 09:59:20 2024 +0800 Add AzPipelineGroup cmdlets (#26197) * Add PipelineGroup module * Add docs * Rebuild module * Update tests * Update test recordings --------- Co-authored-by: Jingchuan Huang [email protected]

Checklist

• [x] 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