tests: Improve the kbs_k8s_delete function

[GabyCT]

This PR improves the kbs_k8s_delete function to verify that the resources were properly deleted for baremetal environments.

Fixes #9379

[GabyCT]

@wainersm besides the pod, do you want me to verify the deployment and the configmaps?

[wainersm]

Hi @GabyCT ! Hey, thanks for working on it!

@wainersm besides the pod, do you want me to verify the deployment and the configmaps?

Notice that currently we only have support for the AKS ingress, but after the merge of #9273 we will have the nodeport too.

The AKS's ingress will install daemonsets too IIRC and we will need to check they were over. The nodeport ingress model will only deploy a service which I don't believe we should check it is deleted.

[GabyCT]

@wainersm I tested this PR on a baremetal environment and seems working as it verifies the nodeport and aks

kubectl get all -n coco-tenant
NAME                       READY   STATUS    RESTARTS   AGE
pod/kbs-757974bf88-gmz82   1/1     Running   0          63s

NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
service/kbs            ClusterIP   10.43.172.228   <none>        8080/TCP         24m
service/kbs-nodeport   NodePort    10.43.27.84     <none>        8080:30353/TCP   63s

NAME                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/kbs   1/1     1            1           24m

NAME                             DESIRED   CURRENT   READY   AGE
replicaset.apps/kbs-757974bf88   1         1         1       63s
replicaset.apps/kbs-5ff79d7849   0         0         0       24m

After running the PR, I verify that both nodeport and aks was gone on the baremetal

[GabyCT]

/test