Kuberay CRDs cause crash of MultiKueue integration tests setup

[mszadkow]

What happened:
Attempt to add CRDs of Kuberay to multikueue integration tests cause them to stuck and fail.
Integration tests CI never finishes due to reported issues.

  panic: Your Test Panicked
        callback[0]()
        /Users/michal_szadkowski/workspace/kueue/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:323
          When you, or your assertion library, calls Ginkgo's Fail(),
          Ginkgo panics to prevent subsequent assertions from running.
  
          Normally Ginkgo rescues this panic so you shouldn't see it.
  
          However, if you make an assertion in a goroutine, Ginkgo can't capture the
          panic.
          To circumvent this, you should call
  
                defer GinkgoRecover()
  
          at the top of the goroutine that caused this panic.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Add CRDs of Kuberay to MultiKueue integration tests in createCluster() as another DepCRDPath.

func createCluster(setupFnc framework.ManagerSetup, apiFeatureGates ...string) cluster {
	c := cluster{}
	c.fwk = &framework.Framework{
		CRDPath:     filepath.Join("..", "..", "..", "config", "components", "crd", "bases"),
		WebhookPath: filepath.Join("..", "..", "..", "config", "components", "webhook"),
		DepCRDPaths: []string{filepath.Join("..", "..", "..", "dep-crds", "jobset-operator"),
			filepath.Join("..", "..", "..", "dep-crds", "training-operator-crds"),
			filepath.Join("..", "..", "..", "dep-crds", "mpi-operator"),
			filepath.Join("..", "..", "..", "dep-crds", "ray-operator-crds"),
		},
		APIServerFeatureGates: apiFeatureGates,
	}

Minimal reproduction scenario is available in this PR.

Anything else we need to know?:

The issue have been investigated by @mszadkow, @mbobrovskyi and @mimowo.
The only thing that makes the tests to pass was to reduce the number of INTEGRATION_NPROCS which could be described as "hacky".
Also we don't know why this workaround works.

Seems that problem is solely connected to Kuberay CRDs, there were attempts to add more CRDs from different sources, which didn't cause the same issue.

Environment:

• Kubernetes version (use kubectl version):
• Kueue version (use git describe --tags --dirty --always):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others: