cmk create kubernetescluster serviceofferingid issue (CKS)

### problem

When using cmk to create kubernetescluster with nodeoffering, I left out the serviceofferingid (the legacy parameter pre 4.21) which I thought was optional as it will be overwritten with nodeoffering anyway.
The CKS was created sucessfully but when I try to upgrade the kubernetes cluster, I get the error "Invalid service offering associated with Kubernetes cluster". The upgrade seems to check for serviceofferingid and require it to be present even though you can create one without serviceofferingid.

A second related issue is when I put a serviceofferingid of a 1 vcpu 1 GB ram in cmk create kubernetescluster as a way to pass the upgrade check. To my suprise, when I try to upgrade, cloudstack complains that the template does not meed minimum hardware requirement even though the template I put in to nodeoffering satisfy this requirement. So it must be using serviceofferingid to verify the hardware requirement when upgrade was triggered.

### versions

4.22.1 KVM NFS

### The steps to reproduce the bug

1. use cmk (or api) to create cks with nodeoffering ommiting serviceofferingid
2. Try to upgrade CKS
3.
...

### What to do about it?

The correct behaviour for the upgrade process is to also check for the presence of nodeoffering and use this to detect minimum hardware requirement

Reproduce el problema con cmk o la API en CloudStack 4.22.1: crea un clúster de Kubernetes con un nodeoffering pero sin serviceofferingid y, a continuación, intenta realizar una actualización. Sigue la ruta de actualización del clúster de Kubernetes y compara cómo se valida serviceofferingid frente a nodeoffering. El trabajo estará terminado cuando las actualizaciones utilicen nodeoffering cuando esté presente y validen correctamente sus requisitos mínimos de hardware.

Escrito por el modelo de indexación a partir del texto del issue.