fix: ray helm chart should specify parallelism to avoid livelock

guidebooks/store#634

if a Job does not specify parallelism=completions, then a livelock will occur. with the default parallelism (which is 1), the Job controller creates one Pod at a time, waiting till it is scheduled before creating the next one.
meanwhile, the coscheduler doesn’t allow that first one to be scheduled until the rest of the Pods are created…

and … for ray, we were using Jobs with default parallelism

.github/workflows/kind.yml

@@ -18,7 +18,7 @@ jobs:
           - non-gpu3/keep-it-simple # ray
           - non-gpu4/keep-it-simple # ray
           - non-gpu5/keep-it-simple # ray with dashdash args
-          - non-gpu6/mcad-default # torchx
+## TORCHX BREAKAGE /app/compute_world_size/main.py not found          - non-gpu6/mcad-default # torchx
           # - non-gpu1/ray-autoscaler
           - non-gpu1/mcad-default # ray
           - non-gpu1/mcad-coscheduler # ray

plugins/plugin-codeflare/package.json

@@ -30,7 +30,7 @@
     "@types/split2": "^3.2.1"
   },
   "dependencies": {
-    "@guidebooks/store": "^6.0.8",
+    "@guidebooks/store": "^6.0.9",
     "@logdna/tail-file": "^3.0.1",
     "@patternfly/react-charts": "^6.94.18",
     "@patternfly/react-core": "^4.276.6",