docs: Support JobDeploymentStatus as deletion condition

Signed-off-by: JiangJiaWei1103 <waynechuang97@gmail.com>

Author: JiangJiaWei1103

ray-operator/config/samples/ray-job.deletion-rules.yaml

@@ -12,6 +12,12 @@ spec:
   # DeletionStrategy defines the deletion policies for a RayJob.
   # It allows for fine-grained control over resource cleanup after a job finishes.
   # DeletionRules is a list of deletion rules, processed based on their trigger conditions.
+  # Currently, both JobStatus and JobDeploymentStatus are supported as deletion conditions:
+  # - JobStatus (application-level): Match the Ray job execution status.
+  #   - Currently, only "SUCCEEDED" and "FAILED" are supported.
+  # - JobDeploymentStatus (infrastructure-level): Match the RayJob deployment lifecycle status. This is particularly useful for cleaning up resources when Ray jobs fail to be submitted.
+  #   - Currently, only "Failed" is supported.
+  # For each deletion rule, exactly one of JobStatus and JobDeploymentStatus must be specified.
   # While the rules can be used to define a sequence, if multiple rules are overdue (e.g., due to controller downtime),
   # the most impactful rule (e.g., DeleteCluster) will be executed first to prioritize resource cleanup and cost savings.
   deletionStrategy: