Add Multi-Kueue support to AppWrapper integration

[dgrove-oss]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adds multikueue adapter to appwrappers integration.

Which issue(s) this PR fixes:

Fixes #3989

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dgrove-oss
Once this PR has been reviewed and has the lgtm label, please assign mimowo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	1502079
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/678ad66509760800087d59d4

[mimowo]

/cc @mszadkow for a review pass who is working recently on the integration for KubeRay

[k8s-ci-robot]

@mimowo: GitHub didn't allow me to request PR reviews from the following users: a, review, pass, who, on, the, KubeRay, is, working, recently, for.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @mszadkow for a review pass who is working recently on the integration for KubeRay

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mszadkow]

Remember to add to list of supported prebuiltWorkloads in validation.go

[dgrove-oss]

/hold

[dgrove-oss]

I think to implement the proper managedBy defaulting for AppWrapper, I need to stop using the job framework's default webhook and switch back to a custom one (as in Job and JobSet) that include the managed by logic.

Is this the right approach, or should I look to generalize the base webhook so that it can incorporate optionally setting managedBy via an extension of GenericJob API? Perhaps by defining a JobWithManagedBy interface that had setters and getters

[k8s-ci-robot]

@dgrove-oss: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kueue-test-multikueue-e2e-main	1502079	link	true	/test pull-kueue-test-multikueue-e2e-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.