Update portal for AI Landing Zone Bicep v2.5.2

[placerda]

A new AI Landing Zone Bicep release is available: Azure/bicep-ptn-aiml-landing-zone v2.5.2.

Portal update needed

• Update the Portal release/catalog metadata from Bicep v2.5.1 to v2.5.2.
• Regenerate portal/wrappers/avm.res.maintenance.maintenance-configuration.json from the new release source.
• Verify the generated wrapper forwards the complete Maintenance Configuration contract to AVM 0.3.1:
  • maintenanceScope
  • maintenanceWindow
  • extensionProperties
  • installPatches
  • namespace
  • visibility
  • enableTelemetry
  • lock
  • roleAssignments
  • tags
• Re-enable and correctly map the Jump VM and Build VM maintenance options in the Portal form.
• Keep schedule fields nested under maintenanceWindow and reboot/patch settings under installPatches.

Why this matters

The current generated wrapper forwards only name, location, and tags. A caller requesting maintenanceScope: InGuestPatch therefore receives the AVM default Host scope. Assigning that configuration to a non-isolated VM such as Standard_D4as_v5 fails with UnsupportedResourceOperation.

Validation required

• Confirm omitted properties preserve the AVM 0.3.1 defaults.
• Deploy both Jump VM and Build VM maintenance configurations using maintenanceScope: InGuestPatch.
• Validate assignments against non-isolated VM SKUs.
• Confirm the resulting Maintenance Configuration retains its schedule, extension properties, patch classifications, and reboot preference.

Source fix: Azure/bicep-ptn-aiml-landing-zone#122

Implementation PR: Azure/bicep-ptn-aiml-landing-zone#137

Release notes: https://github.com/Azure/bicep-ptn-aiml-landing-zone/releases/tag/v2.5.2