Cluster not accessible even if I pick the correct config file

[adietish]

related to #4816

Steps:

1. ASSERT: have several config files. I created kind.yaml by launching the kind cluster via Podman Desktop, which created the file config. I then copied it over to kind.yaml and created config with the content that you see below:

config:

---
apiVersion: "v1"
kind: "Config"
current-context: "kind-kind-cluster"
preferences: {}

kind.yaml:

---
apiVersion: "v1"
kind: "Config"
clusters:
- cluster:
    certificate-authority-data: "XXXXX"
    server: "https://127.0.0.1:63039/"
  name: "kind-kind-cluster"
contexts:
- context:
    cluster: "kind-kind-cluster"
    namespace: "default"
    user: "kind-kind-cluster"
  name: "kind-kind-cluster"
current-context: "kind-kind-cluster"
preferences: {}
users:
- name: "kind-kind-cluster"
  user:
    client-certificate-data: "XXXXX"
    client-key-data: "XXXXXXX"

2. EXEC: launch vscode-openshift
3. ASSERT: you are prompted to select a config file

4. EXEC: pick kind.yaml

Result:
vscode-openshift doesnt see my cluster.

kind.yaml is valid: if I copy kind.yml to config, vscode-openshift works fine:

[vrubezhny]

@adietish This should be fixed with #4816 (No need to pick up a single Kube config from the $KUBECONFIG env. variable anymore).
So, closing this one. Feel free to reopen if the issue still can be reproduced when multiple Kube configs used.