`kconnect to` doesn't respect `-k --kubeconfig`

[Lubricy]

What happened: kconnect to my-alias --password $pass -k custom/cubeconfig/path writes kubeconfig to default kubeconfig path instead of custom/cubeconfig/path

What did you expect to happen: kconnect to respects-k --kubeconfig flag and writes to the path specified.

How to reproduce it: touch ~/test.config kconnect to my-alias -k ~/test.config expect kubeconfig writes to ~/text.config

Anything else you would like to add: in file pkg/app/to.go:48 params *ConnectToInput contains the passed in KubernetesConfig but not passed to useParams.

Environment:

• kconnect version (use kconnect version): kconnect - the Kubernetes Connection Manager CLI {"version": "0.5.2"} version: 0.5.2 builddate: "2021-04-01T11:21:32Z" commithash: b37ccf92c51b660c3452a0be6c81f4052258a4e8 goversion: go1.15.10 platform: darwin/amd64 compiler: gc
• Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T17:56:19Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}
• OS (e.g. from /etc/os-release): macOS Big Sur Version 11.4
• Target environment (e.g. EKS, AKS, Rancher): EKS
• Authentication Used (e.g. SAML, IAM, Azure AD):
  SAML