[Az.Dns] Update generation tool version: autorest.powershell v3->v4

[lijinpei2008]

Description

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
  • 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.
  • 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

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[lijinpei2008]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[github-actions]

To the author of the pull request,
This PR was labeled "Breaking Change Release" because it contains breaking changes.

• According to our policy, breaking changes can only take place during major release and they must be preannounced.
• Please follow our guide on the detailed steps.
• Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

[Copilot]

Pull Request Overview

This PR updates the Azure DNS module's AutoRest PowerShell generation tool from version 3 to version 4. The upgrade involves regenerating the DNSSEC configuration cmdlets and updating related documentation files to reflect changes in the generated code structure and API signatures.

• Updated AutoRest PowerShell generation tool from v3 to v4
• Regenerated DNSSEC configuration cmdlets with updated API models and type signatures
• Updated help documentation to reflect new model types and simplified descriptions

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tools/StaticAnalysis/Exceptions/Az.Dns/BreakingChangeIssues.csv	Added breaking change exceptions for type signature changes in DNSSEC cmdlets
src/Dns/Dns/help/*.md	Updated help documentation with simplified descriptions and new model types
src/Dns/Dns/Az.Dns.psd1	Updated generation date metadata
src/Dns/Dns.sln	Updated project GUID references for regenerated AutoRest project
src/Dns/Dns.Autorest/generate-info.json	Updated generation ID for new AutoRest run
src/Dns/Dns.Autorest/docs/*.md	Updated AutoRest documentation with new module GUID and simplified descriptions
src/Dns/Dns.Autorest/README.md	Removed v3-specific configuration directives for AutoRest

Comments suppressed due to low confidence (1)

src/Dns/Dns.Autorest/README.md:1

• The removal of AutoRest v3 configuration is correct for the upgrade to v4, but according to the coding guidelines, this change should be validated by performing a full build and manual testing of the DNSSEC cmdlets to ensure the v4 generation produces working PowerShell commands that can successfully interact with Azure DNS services.

<!-- region Generated -->

[Copilot]

This breaking change exception indicates a significant API change where SigningKey property changed from a single object to a collection. According to the coding guidelines, breaking changes in AutoRest-generated modules should be carefully validated through manual testing scenarios to ensure the new collection-based API works correctly with real Azure DNS DNSSEC configurations.