Update component versions for CAPI, Kind, and other dependencies

[thunderboltsid]

Now that our EL9 build clusters are up and running and we can use newer versions of kind to spin up bootstrap cluster, we can finally update the CAPI, Kind, and other component versions in our toolchain.

• Update CAPI to v1.6.2
• Update Kind to v0.22.0
• Update Kubernetes client-go to v0.29.2
• Update Go to v1.22.1
• Update Ko to v0.15.2
• Update kubernetes-controller-tools to 0.13.0
• Update customise to v5.3.0
• Update yamllint to v1.3.5

Due to modification of versions certain small code changes had to account for new constants and function signatures in newer dependencies. However that triggered failures in our codecov as a lot of these changes were in main.go. As a result, main.go had to be refactored to be more unit-testable to increase code coverage to hit the patch coverage prerequisite.

Note: --metrics-bind-address flag has been removed and --diagnostics-address and --insecure-diagnostics have been added instead.

How has this been tested?

• Prior to adding new EL9 build-clusters to our prow infra, the e2es were failing for this PR. Update component versions for CAPI, Kind, and other dependencies #383 (comment)
• After adding new EL9 build-clusters to our prow infra, the same e2es are passing for this PR.

[thunderboltsid]

/hold

[codecov]

Codecov Report

Attention: Patch coverage is 76.19048% with 15 lines in your changes are missing coverage. Please review.

Project coverage is 25.63%. Comparing base (55e8e38) to head (1c95fc9).

Files	Patch %	Lines
main.go	77.58%	13 Missing ⚠️
controllers/nutanixmachine_controller.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #383      +/-   ##
==========================================
+ Coverage   20.37%   25.63%   +5.25%     
==========================================
  Files          17       19       +2     
  Lines        1212     1303      +91     
==========================================
+ Hits          247      334      +87     
- Misses        965      969       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[thunderboltsid]

/retest

[thunderboltsid]

This is the underlying failure before the CI build cluster upgrade

INFO: Creating a kind cluster with name "test-q1ktgr"
Creating cluster "test-q1ktgr" ...
 • Ensuring node image (kindest/node:v1.27.1) 🖼  ...
 ✓ Ensuring node image (kindest/node:v1.27.1) 🖼
 • Preparing nodes 📦   ...
 ✗ Preparing nodes 📦 
  INFO: Failed to collect logs from kind: [command "docker exec --privileged test-q1ktgr-control-plane sh -c 'tar --hard-dereference -C /var/log/ -chf - . || (r=$?; [ $r -eq 1 ] || exit $r)'" failed with error: exit status 1, [command "docker exec --privileged test-q1ktgr-control-plane journalctl --no-pager -u kubelet.service" failed with error: exit status 1, command "docker exec --privileged test-q1ktgr-control-plane journalctl --no-pager" failed with error: exit status 1, command "docker exec --privileged test-q1ktgr-control-plane crictl images" failed with error: exit status 1, command "docker exec --privileged test-q1ktgr-control-plane journalctl --no-pager -u containerd.service" failed with error: exit status 1, command "docker exec --privileged test-q1ktgr-control-plane cat /kind/version" failed with error: exit status 1]]
  �[38;5;9m[FAILED]�[0m in [SynchronizedBeforeSuite] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.6.2/framework/bootstrap/kind_provider.go:183 �[38;5;243m@ 02/23/24 02:22:51.838�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [56.569 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243m/home/prow/go/src/github.com/nutanix-cloud-native/cluster-api-provider-nutanix/test/e2e/e2e_suite_test.go:63�[0m

  �[38;5;9m[FAILED] Failed to create kind cluster "test-q1ktgr": command "docker run --name test-q1ktgr-control-plane --hostname test-q1ktgr-control-plane --label io.x-k8s.kind.role=control-plane --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run --volume /var --volume /lib/modules:/lib/modules:ro -e KIND_EXPERIMENTAL_CONTAINERD_SNAPSHOTTER --detach --tty --label io.x-k8s.kind.cluster=test-q1ktgr --net kind --restart=on-failure:1 --init=false --cgroupns=private --publish=127.0.0.1:43709:6443/TCP -e KUBECONFIG=/etc/kubernetes/admin.conf kindest/node:v1.27.1" failed with error: exit status 125
  WARNING: Your kernel does not support cgroup namespaces.  Cgroup namespace setting discarded.
  125a72046af9e1b497c484ed5327bc245fee1ec2d935fdbae313d777bd7b6b64
  docker: Error response from daemon: OCI runtime create failed: cgroup namespaces aren't enabled in the kernel: unknown.

Next week we are planning on adding a new build cluster to prow that's a EL9 NKE-X which shouldn't have this issue.

[thunderboltsid]

/hold cancel

[thunderboltsid]

/test e2e-capx-conformance

[thunderboltsid]

/test e2e-k8s-upgrade

[thunderboltsid]

/test e2e-capx-controller-upgrade

[thunderboltsid]

/retest

[thunderboltsid]

/hold

[thunderboltsid]

/retest

[thunderboltsid]

/test e2e-capx-conformance

[thunderboltsid]

the PE credentials had expired causing CSI failures and had to be rotated.
/test e2e-capx-conformance

[thunderboltsid]

/hold cancel

[thunderboltsid]

/retest

[deepakm-ntnx]

@thunderboltsid assuming we did verify with following:

• https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.3-to-v1.4
• https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.4-to-v1.5
• https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.5-to-v1.6

[thunderboltsid]

/retest

[thunderboltsid]

/test e2e-k8s-conformance

[tuxtof]

/lgtm /approve