fix: update prompts in YAML files to guide users on fixing the environment

Author: rinormaloku

.github/data/agent-framework/backup/configmap-misspelled.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v3' service.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch deployment backend-v3 --context ${CLUSTER_CTX} -p '{"spec":{"template":{"spec":{"volumes":[{"name":"backend-v3-code","configMap":{"name":"backend-v3-code-cm"}}]}}}}'

.github/data/agent-framework/backup/configmap-readonly.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v1' service.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl --context ${CLUSTER_CTX} apply -f - <<EOF

.github/data/agent-framework/backup/deployment-env-mismatch.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v3' service. 
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl --context ${CLUSTER_CTX} set env deployment/mysql-v1 MYSQL_ROOT_PASSWORD=mynewpassword

.github/data/agent-framework/backup/deployment-impossible-pod-affinity.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v1' service. 
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch deployment/backend-v1 --context ${CLUSTER_CTX} --type merge -p "

.github/data/agent-framework/backup/deployment-low-resources.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v3' service. 
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch deployment mysql-v1 --context ${CLUSTER_CTX} -p '{"spec":{"template":{"spec":{"containers":[{"name":"mysql","resources":{"limits":{"memory":"10Mi"}}}]}}}}'

.github/data/agent-framework/backup/deployment-pod-affinity-wrong-key.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v1' service. 
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch deployment/backend-v1 --context ${CLUSTER_CTX} --type merge -p "

.github/data/agent-framework/backup/missing-service-selector.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues in the 'backend-v2' service.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch service backend-v2 --context ${CLUSTER_CTX} -p '{"spec":{"selector": null}}'

.github/data/agent-framework/backup/network-policy.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see an error message telling about issues communicating with other services.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl apply --context ${CLUSTER_CTX} -f - <<EOF

.github/data/agent-framework/backup/pod-hostport-conflict.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see backend-v2 pods stuck in pending state when scaling up.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl patch deployment backend-v1 --context ${CLUSTER_CTX} -p '{"spec":{"template":{"spec":{"containers":[{"name":"backend","ports":[{"containerPort": 8080, "hostPort": 28080}]}]}}}}'

.github/data/agent-framework/backup/pod-limit-range-exceeded.yaml

@@ -7,7 +7,7 @@ spec:
   prompt: |
     There is a kubernetes cluster running in context 'kind-kagent'.
     Calling the frontend service at http://frontend-v1:8080 I see backend-v3 pods failing to create due to limit range.
-    You can find a mocha file 'test.js' in the directory $(git rev-parse --show-toplevel)/.github/data/agent-framework/scenario1
+    To make sure you fixed the environment run the tool `checkKubernetesClusterFixed`. And you have my permission to keep trying out things until you fix the environment and all tests pass.
   steps:
     - run: |
         kubectl apply --context ${CLUSTER_CTX} -f - <<EOF