Modernize golang dependencies like controller-runtime and k8s

[qinqon]

Is this a BUG FIX or a FEATURE ?:

/kind enhancement

What this PR does / why we need it:
The golang dependencies are quite old and at unmaintained versions, this change bumps the bigs ones like controller-runtime and k8s to the new ones.

Modernize golang dependencies

[qinqon]

/retest

[qinqon]

/retest

[mkowalski]

/test pull-kubernetes-nmstate-e2e-handler-k8s

Some tests failed with an incorrect result

[qinqon]

Somehow is not able to configure back the initial network state

 [FAILED] Timed out after 120.004s.
  Test didn't return to initial state on node node01
  Expected
      <string>: {
        "eth0": "up",
        "eth1": "up",
        "eth2": "up",
        "lo": "up"
      }
  to match JSON of
      <string>: {
        "eth0": "up",
        "eth1": "down",
        "eth2": "down",
        "lo": "up"
      }

  first mismatched key: "eth2"
  In [AfterEach] at: /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/main_test.go:130 @ 02/13/25 16:38:11.122
  < Exit [AfterEach] TOP-LEVEL - /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/main_test.go:123 @ 02/13/25 16:38:11.123 (2m0.012s)
  > Enter [ReportAfterEach] TOP-LEVEL - /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/main_test.go:139 @ 02/13/25 16:38:11.123
  < Exit [ReportAfterEach] TOP-LEVEL - /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/main_test.go:139 @ 02/13/25 16:38:16.405 (5.282s)
• [FAILED] [154.706 seconds]
TOP-LEVEL [AfterEach]
/tmp/knmstate/kubernetes-nmstate/test/e2e/handler/main_test.go:123
  [user-guide] Introduction
  /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/user_guide_test.go:28
    Configuration tutorial
    /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/user_guide_test.go:64
      should succeed executing all the commands
      /tmp/knmstate/kubernetes-nmstate/test/e2e/handler/user_guide_test.go:69

Looks like eth1 and eth2 initially are now down, but our test reset logic set them up, so there is a mismatch between initial state and final state between tests.

UPDATE1: Looks like something we did here end up deploying nmstate at control-plane too, ignoring the nodeSelector at NMstate CR.

UPDATE2: The new apply function at operator was overriding the new object with the old, now is fixed patchin it, I also found that we are missing the patching operation are coreos monitor resource.

[qinqon]

/retest

[kubevirt-bot]

@qinqon: 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-kubernetes-nmstate-e2e-handler-k8s-future	733b2c0	link	false	/test pull-kubernetes-nmstate-e2e-handler-k8s-future

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.

[mkowalski]

/lgtm

Passed downstream tests as openshift#565

[mkowalski]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkowalski

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 [mkowalski]

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