Allow for multiple ray clusters while using existing ray operator

[chainlink]

What's changing

This separates out the helm dep conditions for the ray cluster and operator, following the convention of naming the condition after the chart name

Refs #828
Closes #872

How to test it

Steps to test the changes:

Test disabling kuberay-operator

$ helm template lumigator lumigator --set backend.s3Bucket=blah,backend.postgresql.enabled=false,backend.kuberay-operator.enabled=false | kubeval --ignore-missing-schemas
WARN - Set to ignore missing schemas
PASS - lumigator/charts/frontend/templates/nginx-cm.yaml contains a valid ConfigMap (nginx-conf)
PASS - lumigator/charts/backend/templates/service.yaml contains a valid Service (lumigator-backend)
PASS - lumigator/charts/frontend/templates/service.yaml contains a valid Service (lumigator-frontend)
PASS - lumigator/charts/backend/templates/deployment.yaml contains a valid Deployment (lumigator-backend)
PASS - lumigator/charts/frontend/templates/deployment.yaml contains a valid Deployment (lumigator-frontend)
WARN - lumigator/charts/backend/charts/ray-cluster/templates/raycluster-cluster.yaml containing a RayCluster (lumigator-kuberay) was not validated against a schema

Test disabling kuberay-cluster

$ helm template lumigator lumigator --set backend.s3Bucket=blah,backend.postgresql.enabled=false,backend.kuberay-operator.enabled=false,backend.ray-cluster.enabled=false | kubeval --ignore-missing-schemas
WARN - Set to ignore missing schemas
PASS - lumigator/charts/frontend/templates/nginx-cm.yaml contains a valid ConfigMap (nginx-conf)
PASS - lumigator/charts/backend/templates/service.yaml contains a valid Service (lumigator-backend)
PASS - lumigator/charts/frontend/templates/service.yaml contains a valid Service (lumigator-frontend)
PASS - lumigator/charts/backend/templates/deployment.yaml contains a valid Deployment (lumigator-backend)
PASS - lumigator/charts/frontend/templates/deployment.yaml contains a valid Deployment (lumigator-frontend)

Additional notes for reviewers

Anything you'd like to add to help the reviewer understand the changes you're proposing.

I already...

• Tested the changes in a working environment to ensure they work as expected
• Added some tests for any new functionality
• Updated the documentation (both comments in code and product documentation under /docs)
• Checked if a (backend) DB migration step was required and included it if required