Recreate kind cluster on every evg host reboot

[lucian-tosa]

Summary

Evergreen hosts reboot every day or weekend (depending on your configuration). After every reboot, inter-cluster connectivity might be broken for some reason. Recreating the clusters is the only solution we have so far.
This is a systemd service that runs on every boot and recreates all clusters (including the kind-kind for single cluster tests).
Our tunnel command will now also get the kubeconfig from the host otherwise the tunnel won't open to the (new) ports of the recreated clusters.

The systemd service is not created by default. This needs to be explicitly done by running

evg_host.sh configure --auto-reboot

Remove the architecture flag, and instead left it to be inferred from uname.

Proof of Work

Tested locally, but it would be nice if someone can checkout this branch and try it for themselves.

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 checked for release_note changes?

[SimonBaeumer]

I am split on this change, it risks loosing data or setups... I understand the desire to fix this, but on the other hand I don't like when my environment gets cleaned up automatically when it was still in use. For example, if I had run patches against deployments or single cluster deployments my environment will be resetted.

Can you add an env var to opt-in for this re-creation? Than each engineer can decide whether they want re-creation or not.

[github-actions]

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

MCK 1.5.0 Release Notes

New Features

• Improve automation agent certificate rotation: the agent now restarts automatically when its certificate is renewed, ensuring smooth operation without manual intervention and allowing seamless certificate updates without requiring manual Pod restarts.

Bug Fixes

• MongoDBMultiCluster: fix resource stuck in Pending state if any clusterSpecList item has 0 members. After the fix, a value of 0 members is handled correctly, similarly to how it's done in the MongoDB resource.
• MultiClusterSharded: Blocked removing non-zero member cluster from MongoDB resource. This prevents from scaling down member cluster without current configuration available, which could lead to unexpected issues.

Added flag

[lsierant]

LGTM! Trying it out immediately!