Rigid binding to KUBECONFIG env variable causes unit tests failures in some environments

[ardaguclu]

As seen in here https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_openshift-mcp-server/21/pull-ci-openshift-openshift-mcp-server-main-test/1957772596984418304 (PR: openshift#21), CI pipeline in OpenShift automatically sets its KUBECONFIG environment variable. Relying on KUBECONFIG in unit tests cause unexpected failures.

we need to pass fake kubeconfig via StaticConfig instead of modifying KUBECONFIG (i.e. os.Setenv("KUBECONFIG", kubeConfig)) to have a reliable unit tests that work on various environments.

[ardaguclu]

I'm trying to fix it.

[ardaguclu]

This WIP PR openshift#21 tries to fix the KUBECONF env var dependencies by moving to kubeConfig arguments passed by. Seems to be passing.

However, tests that is about empty namespaces (trying to exercise the default namespace) are still failing.

As a result, tests currently broken in openshift-mcp-server repository.

[ardaguclu]

Tests passed openshift#21. Resolution is to skip all these tests. I'll open a PR in downstream to filter out these tests only for OpenShift CI.