Validate cluster cloud labels

[olemarkus]

Users can now set labels such as Name on all resources kOps creates. This breaks consequtive runs of kops update cluster as kOps cannot find its resources.

Fixes #10596

[hakman]

/test pull-kops-e2e-kubernetes-aws
/test pull-kops-e2e-k8s-containerd

[hakman]

Looks good from my point of view. Not sure if message can be improved.
/lgtm
/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, olemarkus

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman,olemarkus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rifelpet]

We should apply the same validation to the instance group cloud labels

[olemarkus]

kOps sets the reserved names before validation so there we already check that this value has not been changed. We could (should) change this behaviour so that these labels are not "sent through" the cluster spec. Then we could pass both maps through the same validation function.

[hakman]

/lgtm
/hold cancel

[hakman]

/retest