LWS validation currently happens late in the lifecycle. The system only verifies the LWS installation after the user has configured the Kueue hierarchy (ResourceFlavor, ClusterQueue, Namespace, LocalQueue, etc) and attempts to apply a template. This results in late-stage failure feedback for the user.

Steps to Reproduce:

• Install Kueue Operator
• On Kueue Operand CR add LeaderWorkerSet 
• Check that configMap "kueue-manager-config" is updated with LWS info
• Create a Resource Flavor and ClusterQueue
• Create a Namespace and add a LocalQueue
• Apply a LWS template
• The following error should be shown:

error: resource mapping not found for name: "lws-and-workers" namespace: "test-lws" from "leaderworkerset.yaml": no matches for kind "LeaderWorkerSet" in version "leaderworkerset.x-k8s.io/v1"
ensure CRDs are installed first

Current Behavior: Validation is deferred. Currently, LWS is only validated after the Operand CR is updated and the full Kueue hierarchy (ResourceFlavor, ClusterQueue, and LocalQueue) is established. Users only discover configuration errors at the final step when applying an LWS template.

Proposed Change: Shift validation earlier in the process for better user experience. Validation can occur immediately when LWS is added to the Operand CR. This ensures the environment is "good" before the user invests time in configuring the queuing resources.