Update cloud job cleanup scripts for correct secret access (#6503)

Added sudo to the clean job script to align with the login process and ensure correct
access to the necessary secrets. The clean job was failing to access the correct secrets
because it was not using sudo, whereas the login process used with Jenkins account.

Signed-off-by: Shuyang Xin <gavinx@vmware.com>

ci/jenkins/jobs/macros.yaml

@@ -28,15 +28,15 @@
       - shell: |-
          #!/bin/bash
          set -ex
-         ./ci/test-conformance-gke.sh --gcloud-sdk-path "${GCLOUD_SDK_PATH}" --cluster-name "${CLUSTERNAME}" --cleanup-only
+         sudo ./ci/test-conformance-gke.sh --gcloud-sdk-path "${GCLOUD_SDK_PATH}" --cluster-name "${CLUSTERNAME}" --cleanup-only
 
 - builder:
     name: builder-aks-cluster-cleanup
     builders:
       - shell: |-
          #!/bin/bash
          set -ex
-         ./ci/test-conformance-aks.sh --cluster-name "${CLUSTERNAME}" --cleanup-only
+         sudo ./ci/test-conformance-aks.sh --cluster-name "${CLUSTERNAME}" --cleanup-only
 
 - builder:
     name: builder-workload-cluster-garbage-collection