[Az.Dns] Add NAPTR support and tests

[WhiteHorseV]

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

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

❌Az.Dns

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

❌Signature Check

❌PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
❌	Add-AzDnsRecordConfig	Parameter Flags of cmdlet Add-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Add-AzDnsRecordConfig	Parameter Services of cmdlet Add-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	New-AzDnsRecordConfig	Parameter Flags of cmdlet New-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	New-AzDnsRecordConfig	Parameter Services of cmdlet New-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Remove-AzDnsRecordConfig	Parameter Flags of cmdlet Remove-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Remove-AzDnsRecordConfig	Parameter Services of cmdlet Remove-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
⚠️	Get-AzDnsDnssecConfig	Get-AzDnsDnssecConfig Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzDnsDnssecConfig	Get-AzDnsDnssecConfig changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

❌Windows PowerShell - Windows

Type	Cmdlet	Description	Remediation
❌	Add-AzDnsRecordConfig	Parameter Flags of cmdlet Add-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Add-AzDnsRecordConfig	Parameter Services of cmdlet Add-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	New-AzDnsRecordConfig	Parameter Flags of cmdlet New-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	New-AzDnsRecordConfig	Parameter Services of cmdlet New-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Remove-AzDnsRecordConfig	Parameter Flags of cmdlet Remove-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
❌	Remove-AzDnsRecordConfig	Parameter Services of cmdlet Remove-AzDnsRecordConfig does not follow the enforced naming convention of using a singular noun for a parameter name.	Consider using a singular noun for the parameter name.
⚠️	Get-AzDnsDnssecConfig	Get-AzDnsDnssecConfig Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzDnsDnssecConfig	Get-AzDnsDnssecConfig changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️File Change Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️		It is required to update ChangeLog.md if you want to release a new version for Az.Dns.	Add a changelog record under Upcoming Release section with past tense.

⚠️Windows PowerShell - Windows

Type	Cmdlet	Description	Remediation
⚠️		It is required to update ChangeLog.md if you want to release a new version for Az.Dns.	Add a changelog record under Upcoming Release section with past tense.

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

❌Test

❌PowerShell Core - Linux

❌PowerShell Core - MacOS

❌PowerShell Core - Windows

❌Windows PowerShell - Windows

️✔️Az.Network

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

[WhiteHorseV]

I will update the test runs after the NAPTR feature is enabled in the PPE/Prod region.