[Feature]: 2024-11-01 API version for Azure Managed HSM

[Cherrett]

Description of the new feature

I am a part of the Azure Managed HSM team. When creating a new Managed HSM resource using New-AzKeyVaultManagedHsm, the SKU defaults to the B family, irrespective of the SKU name specified. This is not correct since we have certain SKUs in the C family.

These are all of the valid Managed HSM SKUs:

B SKU family: Standard_B1, Custom_B32, Custom_B6
C SKU family: Custom_C42, Custom_C10

For Custom_C42 and Custom_C10, the SKU family passed to ARM should be C instead of B.

This can be determined by checking the letter following the underscore in the SKU name.

The new SKUs are included in the Microsoft.KeyVault 2024-11-01 API version. Azure PS should use this API version.

Proposed implementation details (optional)

No response

[notyashhh]

We'll plan this feature in the coming sprints.