feat: Update api versions and add resource derived types for virtual hub

[oZakari]

Description

This pull request updates the Azure Virtual Hub module and its related resources to use the latest API version (2025-01-01) and introduces support for additional resource derived types. The changes ensure improved compatibility with new Azure features and future-proof the module. Parameter definitions and documentation have also been updated to reflect these changes, including the removal of hardcoded allowed values in favor of resource-derived types.

API Version Updates

• Updated all references to Microsoft.Network/virtualHubs, hubRouteTables, hubVirtualNetworkConnections, and related resources to use API version 2025-01-01 in Bicep, JSON, and documentation files. [1] [2] [3] [4] [5] [6] [7]

Resource Derived Types

• Changed parameter definitions for tags, hubRoutingPreference, preferredRoutingGateway, and virtualRouterAsn to use resource-derived types based on the latest API version, improving flexibility and maintainability. [1] [2] [3] [4] [5] [6]

Documentation and Example Updates

• Updated the README documentation and usage examples to reflect new parameters (preferredRoutingGateway, routingIntent, virtualRouterAsn) and the API version change. [1] [2] [3] [4]
• Removed hardcoded allowed values for parameters in documentation, relying on resource-derived types instead. [1] [2]

Changelog

• Added a changelog entry for version 0.4.3, summarizing the API version update and addition of resource derived types.

Miscellaneous

• Minor text correction in the privacy statement in the README.

Pipeline Reference

Pipeline

Type of Change

• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation
• Update to CI Environment or utilities (Non-module affecting changes)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings
• I have updated the module's CHANGELOG.md file with an entry for the next version

[arnoldna]

@oZakari - Looks like there is a problem with the max test changes you made.

[oZakari]

Hey @arnoldna, I think there is actually an issue with the original module or the RP itself. If you try to deploy the module as it is today with hubRoutingPreference it will fail at least in the two tenants I owned. I was hoping it was just an outdated API version, but think it's beyond that. Have you tried setting that property in your environment?

[arnoldna]

@oZakari - let me take a look at the deployment issue.

[arnoldna]

@oZakari - I was able to take the main branch from your repo and was able to deploy without error. both the max and the routing intent tests. I will switch to your branch and will try deploying with your changes.