`gke-gcloud-auth-plugin`: Support overriding `gke_gcloud_auth_plugin_cache` location

[erebe]

Following #554

Issue:

Currently, gke-gcloud-auth-plugin create/use a cache at a fixed location in $HOME/.kube/gke_gcloud_auth_plugin_cache
This cause issue when several accesses using different account is needed, because gke-gcloud-auth-plugin always endup using this cache if present

It would really be nice to have an environment variable to change the location of this cache at least.
As example, when running inside a CI, the fixed path break the isolation per run.
The only workaround is to change HOME variable before executing the command, but this feel unsafe to do with potentially un-intended side effects.

Proposed solution:

Introduce a parameter or an environment variable to change the location of this cache

[k8s-ci-robot]

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale