🌱 e2e: Display path of the kubeconfig file for the bootstrap cluster

[superbrothers]

What this PR does / why we need it:

This PR displays the path of the kubeconfig file for the bootstrap cluster for E2e tests. It makes it easier to debug provider controllers if it fails to initialize the bootstrap cluster.

STEP: Setting up the bootstrap cluster
INFO: Creating a kind cluster with name "test-6lnn2w"
INFO: The kubeconfig file for the kind cluster is /var/folders/d3/lsp0h4wx7wsd4_yrymm9nnm80000gn/T/e2e-kind675530722
STEP: Initializing the bootstrap cluster

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

Hi @superbrothers. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fabriziopandini]

/ok-to-test

[fabriziopandini]

/approve
/milestone v0.3.10

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fabriziopandini]

/cc @sedefsavas

[superbrothers]

/test pull-cluster-api-test

[fabriziopandini]

BTW, while running test locally, I find simpler and faster to use an existing kind cluster instead of creating one for each test run.
Nevertheless, I don't see a problem in getting this change merged because in CI logs will be available only after the cluster is already deleted (and the kubeconfig file won't be accessible)

[superbrothers]

I know we can use an existing kind cluster, but sometimes I want to reference a cluster for various uses, such as an Infrastructure machine creation failure. Also, I know that all objects are dumped on exit, but not all new Infrastructure providers have fully implemented phases and events.

[vincepri]

/lgtm
/milestone v0.3.10