[Feature]: Add availabilityZoneMappings to get-AzLocation

### Description of the new feature

The Azure Rest API for subscrption -> List location has extended information for availabilityZoneMappings that has will shortly be enabled in Bicep.

Please add this to the current get-AzLocation (and possibly the equivalent Az CLI command)

### Proposed implementation details (optional)

Either add this information as an additional object in the return or add a parameter to enable output

```powershell
Get-AzLocation | where-Object { $_.location -eq 'eastus'}

Location : eastus
DisplayName : East US
Type : Region
Longitude : -79.8164
Latitude : 37.3719
PhysicalLocation : Virginia
RegionType : Physical
RegionCategory : Recommended
GeographyGroup : US
PairedRegion : [
{
"Name": "westus",
"Id": "/subscriptions/c5d35f87-827d-4224-85d9-a5fac1b90b9b/locations/westus",
"SubscriptionId": null
}
]
AvailabilityZoneMappings: [
{
"logicalZone": "1",
"physicalZone": "eastus-az1"
},
{
"logicalZone": "2",
"physicalZone": "eastus-az3"
},
{
"logicalZone": "3",
"physicalZone": "eastus-az2"
}
]
},
Providers : {Microsoft.KeyVault, Microsoft.DesktopVirtualization, Microsoft.DBforMySQL, Microsoft.Storage…}
```

Start at the Get-AzLocation cmdlet and inspect how the Azure subscription List location response is represented and exposed. Compare the current output with the availabilityZoneMappings data shown in the issue, then verify that Get-AzLocation returns the mappings for a location such as eastus; consider whether the equivalent Az CLI command is in scope.

Written by the indexing model from the issue text.