[RayService] Directly fail CR if is invalid

[win5923]

Why are these changes needed?

Similar to #3980. We should directly fail the RayService CR when validation fails, rather than continuously requeueing.

kuberay/ray-operator/controllers/ray/rayservice_controller.go

Lines 112 to 116 in d59cbd8

	if err := utils.ValidateRayServiceMetadata(rayServiceInstance.ObjectMeta); err != nil {
	r.Recorder.Eventf(rayServiceInstance, corev1.EventTypeWarning, string(utils.InvalidRayServiceMetadata),
	"The RayService metadata is invalid %s/%s: %v", rayServiceInstance.Namespace, rayServiceInstance.Name, err)
	return ctrl.Result{RequeueAfter: ServiceDefaultRequeueDuration}, err
	}

Also add new RayServiceConditionReason called RayServiceValidationFailed.

Status:
  Conditions:
    Last Transition Time:  2025-11-24T15:48:50Z
    Message:               The RayService metadata is invalid: RayService name should be no more than 47 characters
    Reason:                ValidationFailed
    Status:                False
    Type:                  Ready
  Last Update Time:        2025-11-24T15:48:50Z

Related issue number

Closes #4045

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[machichima]

nit: Can we set the name with strings.Repeat("a", 48) to make it obvious that it exceed 48 characters?

[win5923]

Thanks, fix in 49c3b45.