debug(e2e): add diagnostic step to locate kubeconfig

Add ls and echo diagnostics to understand where ARC runners store
kubeconfig. Include ACTIONS_KUBECONFIG and HOME env vars.
Also add $HOME/.kube to the search paths.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

.github/workflows/e2e.yaml

@@ -48,7 +48,15 @@ jobs:
       - name: Locate kubeconfig for ARC runner
         run: |
           set -euo pipefail
-          for dir in /runner /home/runner/.kube /home/github/.kube; do
+          echo "HOME=${HOME}"
+          echo "ACTIONS_KUBECONFIG=${ACTIONS_KUBECONFIG:-<unset>}"
+          echo "Listing /runner contents:"
+          ls -la /runner/ 2>&1 || echo "/runner does not exist"
+          echo "Listing /home/runner contents:"
+          ls -la /home/runner/ 2>&1 || echo "/home/runner does not exist"
+          echo "Listing /home/github contents:"
+          ls -la /home/github/ 2>&1 || echo "/home/github does not exist"
+          for dir in /runner /home/runner/.kube /home/github/.kube "$HOME/.kube"; do
             if [ -f "${dir}/config" ]; then
               echo "Found kubeconfig at ${dir}/config"
               echo "KUBECONFIG=${dir}/config" >> "$GITHUB_ENV"
@@ -56,7 +64,7 @@ jobs:
             fi
           done
           if [ -z "${KUBECONFIG:-}" ]; then
-            echo "::error::No kubeconfig found for ARC runner. Checked: /runner, ~/.kube, ~/kube"
+            echo "::error::No kubeconfig found for ARC runner"
             exit 1
           fi
           echo "Using kubeconfig: ${KUBECONFIG}"