Add machineNaming support to MachineDeploymentClass and MachineDeploymentTopology

[danylomikula]

What would you like to be added (User Story)?

machineNaming field from MachineDeploymentSpec should be exposed in MachineDeploymentClass and MachineDeploymentTopology so topology-managed clusters can customize Machine names within MachineDeployments.

Detailed Description

machineNaming on MachineDeploymentSpec allows customizing Machine names, but the topology controller doesn't propagate it. There's no way to set it through ClusterClass or Cluster topology.

This means topology-managed MachineDeployments always produce Machine names like cluster-worker-8fh2k-xn4wp (MachineSet name + random suffix). There's no way to simplify this to e.g. cluster-worker-xn4wp.

Proposal: add machineNaming to MachineDeploymentClass with optional override in MachineDeploymentTopology, same as how naming already works for the MachineDeployment object name.

References:

• MachineNamingStrategy on MachineDeploymentSpec: ✨ ClusterClass: Introduce NamingStrategy and allow generating names using go templates #9340
• naming / machineNaming rename: ⚠️ Rename namingStrategy => naming, machineNamingStrategy => machineNaming #12524
• API consistency umbrella: Improve API consistency #12497

Anything else you would like to add?

Same gap applies to MachinePoolClass / MachinePoolTopology.

Label(s) to be applied

/kind feature
/area clusterclass
/area machinedeployment
/area api

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.