[Express Route] IPv6 Global Reach Add/Set-AzExpressRouteCircuitConnection cmdlet changes.

[amwate]

Description

We are in the process of adding support for IPv6 in ExpressRouteCircuitConnectionConfig.

In the process, we have updated the existing PowerShell cmdlet
Add-AzExpressRouteCircuitConnectionConfig to accept another optional parameter AddressPrefixType (that optionally specifies the address family type for the address prefix).

In addition, we also introduced another cmdlet to modify the existing ExpressRouteCircuitConnectionConfig to add a new block IPv6CircuitConnectionConfig as well.
This would be used to update any existing GlobalReach configuration (ExpressRouteCircuitConnection) configurations.

Below is the design PR
https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/451#event-2913187208

This pull request brings in the changes in the powershell sdk.
The relevant swagger changes are to be merged in network-december-release.
Azure/azure-rest-api-specs#8145

NRP changes are already merged.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • 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 -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[isra-fel]

Hi @amwate , please see my inline comments, thanks!

[isra-fel]

Here too

[amwate]

Done. Thanks

[amwate]

The branch had merge conflicts. I have created another review #10990, with a different branch.