Avoid to change user data during e2e tests

During the launch of e2e tests the user `.kube/config` file will be changed, read and changed again for the action caused by launching kind.

It will be best to avoid this using some kind of temporary file for the kubernetes configuration that can be delete and modified as we wish without problems.

Start from the e2e test launch path and the action that launches kind, then trace how the Kubernetes configuration is read and changed. Done means the tests use a temporary Kubernetes configuration and no longer modify the user's .kube/config file.

Written by the indexing model from the issue text.