Always populate kubernetesSpec.{*}.imageRepository fields in TKR_DATA values

[imikushin]

Describe the feature request

imageRepository fields in kubernetesSpec.{etcd,pause,coredns,kube-vip} can be empty. In this case, the clients should be defaulting to kubernetesSpec.imageRepository, BUT: it is not as easy as just having the data already in kubernetesSpec.{*}.imageRepository.

We would allow for simpler ClusterClass JSON patches, if we populate kubernetesSpec.{*}.imageRepository fields in TKR_DATA values.

Describe alternative(s) you've considered

Current situation: ClusterClass authors need to check for empty value and get the value from kubernetesSpec.imageRepository. Sometime they'd forget, and it'd cause of a bug.

Affected product area (please put an X in all that apply)

• (X) APIs
• ( ) Addons
• ( ) CLI
• ( ) Docs
• ( ) IAM
• ( ) Installation
• ( ) Plugin
• ( ) Security
• ( ) Test and Release
• ( ) User Experience
• (X) Developer Experience

Additional context