fix: issue 352 kconnect doesn't respect -k --kubeconfig

[srinathanand]

What this PR does / why we need it: This PR fixes the issue where passing in the -k flag to kconnect to with a custom kubeconfig path honors it instead of writing it to the default kubeconfig path.

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 #352

[seankelly001]

@srinathanand Small issue I have found in the following scenario: kconnect use eks -k /home/user/test/myconfig

User then runs: kconnect to -

Config doesn't store in correct place (/home/user/test/myconfig), it instead stores in the default location. Have verified that latest release of kconnect does indeed store it in the correct location (/home/user/test/myconfig). Could you address this please?

[Gearheads]

This PR is not needed, since #561 fixes the issue.