Translate TopologyConstraints from Grove workload API to scheduler API

[sanjaychatterjee]

What you would like to be added?

Map the topology constraints to cluster specific constraints when creating the PodGang.

Why is this needed?

This is needed to ensure that KAI scheduler will be able to make the TAS optimizations as per the cluster specific constraints defined in the Kueue CR.

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Implement topology constraint translation by adding new file operator/internal/controller/podcliqueset/components/podgang/topology_translator.go (complete 3-level translation logic, auto-generate preferred constraints, add grove.io/topology-name annotation, fetch/validate ClusterTopology, handle errors) and updating operator/internal/controller/podcliqueset/components/podgang/podgang.go to call the translator during PodGang build/updates so PodCliqueSet topologyConstraint is translated into scheduler-ready PodGang topologyConstraint.

• Add topology-aware scheduling translation by creating operator/internal/controller/podcliqueset/components/podgang/topology_translator.go (new) to map PodCliqueSet topology constraints to PodGang (including ClusterTopology lookup, domain→key translation, group and pod-level translations, annotations, and error handling), modify operator/internal/controller/podcliqueset/components/podgang/podgang.go to call the translator during buildResource, and add IMPLEMENTATION_SUMMARY.md documenting the feature and tests.

• ✅ Create PR with these edits
• 📋 Get copyable edits