Use consistent or clearer naming for generated kubeadmconfig and workermachine templates

I would expect these names to be identical but they are not, and the difference between them is only the word `template` which isn't descriptive enough. Either we should use the same naming convention or be more specific like `"%s-%s-worker-machine-template-%d"` and `"%s-%s-kubeadm-config-template-%d"` like we do for etcd and cp.

No file or test is named. Start by locating the code that generates the kubeadmconfig and workermachine template names, then compare its naming with the existing etcd and cp conventions. Done means the affected names use one consistent, descriptive convention and the relevant tests or generated output reflect it.

Written by the indexing model from the issue text.