minimal integration reference change

[kannon92]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Use IntegrationReference instead of strings.

Which issue(s) this PR fixes:

Maybe #4659

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: kannon92
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.

Details

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 ready!

Name	Link
🔨 Latest commit	948a671
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/67db662bc3897f0008fb94f3
😎 Deploy Preview	https://deploy-preview-4697--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kannon92]

/cc @mimowo

#4676 (comment)

[mimowo]

Actually, out of the two I prefer this one in #4676 for consistently using IntegrationReference throughout the codebase where applicable.

My comment was about grouping all the integrations in the monolithic style.

Note that, there is no guarantee when adding a new integration to Kueue someone will put it on the new list. It would compile equally well if the constant was declared in the scope of the package for the new integration.
So, I'm honestly not sure what is the benefit, maybe vs-code support to find all references?. Also, as new integrations are added one needs to be always careful to check code for the tag corresponding to the version of Kueue installed. I think the most reliable source of trough is runtime logging, or a utility function exported by Kueue as suggested earlier. Also, other approaches were proposed as loose validation.

I'm open to the possibility, that I'm missing something, but I would like to take a step back and define the problem we are solving. For example, the issue mentions MXJob, which was not in the comments for a good reason, as no longer supported.

And I think there is no need to rush, we can do it post 0.11, and post KubeCon :) .

/hold
cc @tenzen-y