feat: add ap-south-2 (HYD) ECR regional-values for GPU operator

[svia3]

Add regional-values file for ap-south-2 so customers in Hyderabad can pull GPU operator images from the local ECR mirror (580982410692) during helm install.

ECR account verified via isengardcli: aws-crescendo-dockerregistry+prod-hyd-service

What's changing and why?

Adding values-ap-south-2.yaml to the GPU operator regional-values directory. This is part of the Crescendo region expansion to ap-south-2 (Hyderabad). The ImageReplicator pipeline already replicates GPU operator images to the HYD DockerRegistry ECR account (580982410692), but the helm chart was missing the regional-values file that tells customers where to pull from.

Without this file, customers in ap-south-2 cannot install the GPU operator via the HyperPod helm chart — the CLI has no ECR URI to resolve for that region.

Before/After UX

Before:
Customers in ap-south-2 attempting to install GPU operator via hyperpod connect-cluster or direct helm install get an error because no regional-values file exists for their region.

After:
Customers in ap-south-2 can install the GPU operator normally. The helm chart resolves image pulls to 580982410692.dkr.ecr.ap-south-2.amazonaws.com (the Crescendo-managed ECR mirror in HYD).

How was this change tested?

• Verified ECR account ID (580982410692) via isengardcli cat → confirms aws-crescendo-dockerregistry+prod-hyd-service
• File format matches existing regional-values files (ap-northeast-2, ca-central-1, etc.)
• ImageReplicator pipeline confirmed deployed to HYD DockerRegistry account (Step 8 of region build completed 2026-05-14)

Are unit tests added?

N/A — config-only change (YAML values file).

Are integration tests added?

N/A — GPU partitioning integration tests cannot run in ap-south-2 due to lack of MIG-compatible instance types (p4/p5 not available in HYD). Manual testing will be performed once capacity is available.

Reviewer Guidelines

‼️ Merge Requirements: PRs with failing integration tests cannot be merged without justification.

One of the following must be true:

• All automated PR checks pass
• Failed tests include local run results/screenshots proving they work
• Changes are documentation-only