test(DTR): Testing different K8S versions for DTR (incubation)

[itsfarhan]

This PR is of issue #1909. Currently performing matrix testing with recent minor release k8s versions.

So far what I noticed:

• New versions [1.32, 1.33, 1.34] create clusters and k8gb deployment.
• But terratest took more than usual time and failed in k3d v5.8.3

References:
https://kubernetes.io/releases/

HOW TO RUN CI

---

By default, all the checks will be run automatically. Furthermore, when changing website-related stuff, the preview will be generated by the netlify bot.

Heavy tests

Add the heavy-tests label on this PR if you want full-blown tests that include more than 2-cluster scenarios.

Debug tests

If the test suite is failing for you, you may want to try triggering Re-run all jobs (top right) with debug logging enabled. It will also make the print debug action more verbose.

[ytsarev]

we most probably want to hide matrix testing under 'heavy tests' label to avoid running them on every PR

[abaguas]

The error we are facing is in the creation of the k3d cluster:

ERRO[0005] Failed Cluster Start: Failed to start server k3d-edgedns-server-0: Node k3d-edgedns-server-0 failed to get ready: error waiting for log line `k3s is up and running` from node 'k3d-edgedns-server-0': stopped returning log lines: node k3d-edgedns-server-0 is running=true in status=restarting 

Some research shows a potential mismatch between k3d and the host. What happens if you try to use the default k3d version v5.4.6 instead of upgrading to v5.6.3? I suggest to try to change one thing at a time to understand what is the cause

[itsfarhan]

I have tried with default v5.4.6 version and had same error. Like you suggested I will try to change one at a time and see if it makes it through.