🌱 test/framework: don't fix kubeconfig for remote CAPD clusters

[sbueringer]

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
This PR changes the fix kubeconfig logic so that we only adjust the kubeconfig when necessary.

Specifically it only makes sense to fix the kubeconfig when the CAPD cluster is running locally in Docker Desktop.

It is not necessary if the CAPD cluster is running on a remote host. Actually for remote clusters fixing the kubeconfig breaks the kubeconfig as the remote cluster is not available under 127.0.0.1

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 #

[sbueringer]

/assign @fabriziopandini

[chrischdi]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 8b0e3f56ceeb08f6de1563a3fa0e617bc55d4f4e

[sbueringer]

/retest
(unrelated flake)

/test pull-cluster-api-e2e-full-main

[killianmuldoon]

/lgtm

[fabriziopandini]

/lgtm
/approve

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

@sbueringer, with no rush, let's demo during office hours how to use a remote docker-engine, that's a nice feature to have

[sbueringer]

@sbueringer, with no rush, let's demo during office hours how to use a remote docker-engine, that's a nice feature to have

Yup good idea, will do. Probably after easter in April