Update kind and kindest/node image to latest available versions (1.33.2)

[viveksinghggits]

Summary

As part of the release process, we update the kind and kindest/node to latest available versions. This PR does that.

On EVG environments the script setup_kind_cluster.sh tries to pull the image from the ecr mirror instead of pulling it from docker hub to avoid rate limiting issues. That's why to make sure that CI passes on this PR, we will have to copy the image manually to the ecr from docker hub.
Below command can be used to do that

# use index digest
docker pull kindest/node:v1.33.2@sha256:c55080dc5be4f2cc242e6966fdf97bb62282e1cd818a28223cf536db8b0fddf4
skopeo copy --preserve-digests --all docker://docker.io/kindest/node:v1.33.2 docker://268558157000.dkr.ecr.eu-west-1.amazonaws.com/docker-hub-mirrors/kindest/node:v1.33.2

The index digest on ecr will be same and that's the same digest that can be used in the script.

After this change somehow the test e2e_static_multi_cluster_kind/e2e_multi_cluster_replica_set_migration started failing mainly because of timeout waiting for sts to be ready. And we figured that increasing the timeout is the best path forward. That's why we are also increasing timeout for that test as part of this PR.

Proof of Work

Successful CI run on this PR would prove that the change is good.

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.3.0 Release Notes

New Features

Multi-Architecture Support

We've added comprehensive multi-architecture support for the kubernetes operator. This enhancement enables deployment on IBM Power (ppc64le) and IBM Z (s390x) architectures alongside
existing x86_64 support. Core images (operator, agent, init containers, database, readiness probe) now support multiple architectures. We do not add support IBM and ARM support for Ops-Manager and the init-ops-manager image.

Bug Fixes

• This change fixes the current complex and difficult-to-maintain architecture for stateful set containers, which relies on an "agent matrix" to map operator and agent versions which led to a sheer amount of images.
• We solve this by shifting to a 3-container setup. This new design eliminates the need for the operator-version/agent-version matrix by adding one additional container containing all required binaries. This architecture maps to what we already do with the mongodb-database container.
• Fixed an issue where the readiness probe reported the node as ready even when its authentication mechanism was not in sync with the other nodes, potentially causing premature restarts.

Other Changes

• Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
• subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.
• We have deliberately not published the container images for OpsManager versions 7.0.16, 8.0.8, 8.0.9 and 8.0.10 due to a bug in the OpsManager which prevents MCK customers to upgrade their OpsManager deployments to those versions.

[mircea-cosbuc]

LGTM!