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

[fabriziopandini]

/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/help

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.

[sats-23]

I'd like to take this up!

1. API Changes to MachineDeploymentClass, MachineDeploymentTopology and MachinePoolClass, MachinePoolTopology.
2. Update controller logic and webhook validation logic
3. Tests and Docs

Breaking the implementation into these steps, let me know if anything needs to be improved.

/assign