Decide if we release kjobctl as part of Kueue

[mimowo]

We started to develop kjobctl inside Kueue (cmd/experimental/kjobctl) to get quickly off the ground.

This lets us develop quickly, and may be handy for a while yet.

However, in the long run we discussed that the plan is to move it at some point to a dedicated kubernetes-sigs subproject.

Until that happens - should we release it as part of Kueue release process (exposing the artifacts)?

[mimowo]

/cc @alculquicondor @mwielgus @tenzen-y
I open this as a follow up to #2642.

[tenzen-y]

TBH, I'm ok with either approach. But, I'm wondering if we can create separate repository since I'm not familiar with criterion for new repositories in the k-sigs org.

I just want to say that we should commonize all duplicated scripts as root scripts when we decide to we manage kjobctl in this repository.

[mbobrovskyi]

@alculquicondor WDYT?

[alculquicondor]

We can split after we have the MVP, to avoid disrupting the developer flow.