Bumped versions of k8s dependencies and controller-runtime and k8s dependencies

[NikhilSharmaWe]

What this PR does / why we need it:

This PR bumps versions of k8s dependencies and controller-runtime and k8s dependencies to be compatible with https://github.com/kubernetes-sigs/kubebuilder.

[justinsb]

Thanks @NikhilSharmaWe - looks like there are some breaking API changes in kubectl / cli-utils. I'll take a look!

cc @seans3

[everettraven]

Looks good to me! Great job @NikhilSharmaWe ! Not sure I have permissions for it, but:

/lgtm
/approve

[k8s-ci-robot]

@everettraven: changing LGTM is restricted to collaborators

In response to this:

Looks good to me! Great job @NikhilSharmaWe ! Not sure I have permissions for it, but:

/lgtm
/approve

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/test-infra repository.

[everettraven]

@everettraven Thank you for considering the suggestion. Just wanted to ask how did found out that the base name should be declarative-direct.

It could be any string, but when looking into the details of the apply.NewCmdApply and Apply.ToOptions the baseName is used when printing messages or warnings (can be seen here: https://github.com/kubernetes/kubectl/blob/9a9633e4515045b45600d2e9cc5f0498c5a4d0d1/pkg/cmd/apply/apply.go#L301-L303).

I felt like declarative-direct was descriptive enough to point it to this repo and being in the direct.go file that the setup is being done in.

Now that I think about it, kubebuilder-declarative-applier-direct would be much more descriptive so feel free to change it to that if you would like, but I think the former is still rather descriptive.

[camilamacedo86]

Great 👍
Nice contribution @NikhilSharmaWe and @everettraven 🥇

We need to ping the Owners of this repo so that they can help us move forward.

@justinsb

[camilamacedo86]

/lgtm

[atoato88]

/lgtm

@justinsb
Could you check this?

[everettraven]

@justinsb could you take a look at this?

We have a couple projects relying on this dependency to be upgraded to support k8s 1.24 before they can be upgraded.

Thanks!

[everettraven]

@atoato88 or @justinsb is there anything else that needs to be done to get this merged?

[atoato88]

/approve
Sorry for my delay.
Thank you to create and update PR.

It already looks good for me, and I thinked it is also good to get review from other approver if possible.
But I approve this because this PR is getting time.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atoato88, camilamacedo86, everettraven, NikhilSharmaWe

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [atoato88]

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

[jcanseco]

FYI we started to encounter an issue that seems to have been introduced in this PR: #224

Wondering if anyone can take a look.