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 only action for you is to run evg_host.sh configure which will update the scripts and set up the systemd service.

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?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[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.