Propose to move mesheryctl connections out of experimental

[Rian Cteulp]

Hi,

I would like to help complete the `connection` command. I see that it has a standard set of four subcommands in the command tracker spreadsheet of:

Subcommands

list (done)

delete (complete)

---

view (incomplete)

create (incomplete)

Are there additional subcommands needed or anything special about `view` and `create` that I should consider while assisting here?

Flags

I see the the `--count` flag. Are there additional flags needed beyond the global flags the the `--count` flag that are needed to get this command to a place where it can be promoted out of experimental?

Rian

[Lee Calcote]

Rian, 

This is a timely conversation. Sangram Rath was just noting challenges with the `system config `command (those issues have been fixed), which as it turns out, is a candidate for relocation to the `connection create` command. 

Original Behavior
`system config <k8s-type>`'s original purpose was to allow users to prepare a kubeconfig file for Meshery Server to use to connect to different types of Kubernetes clusters. Previously, you would give it a kubeconfig file and it would prepare a new kubeconfig file compatible with Meshery Server's ongoing use as both a connection and a credential. The command ensured a kubeconfig is generated.

Current Behavior

Currently, `system config <k8s-type>` still receives a kubeconfig file as input, but foregoes responding with a separate kubeconfig file. It still prepares the kubeconfig for Meshery Server's use, but instead I'm returning your file, it takes that file and hand it to me server so that my server creates a new Kubernetes connection and associated credential. Then, it adds the it sets this new Kubernetes connection as an active context in the user's profile.

Proposed Behavior

Relocate the `system config <k8s-type>` logic to `connection create --type <k8s-type>`.

- Lee

[Lee Calcote]

In terms of flags, I will mention that each `connection` needs to have the ability to be tethered to (assigned to) one or more environments. The `environment` command is not in experimental, however, it seems to fail to perform the `list` subcommand properly (https://github.com/meshery/meshery/issues/16684).

- Lee

[Lee Calcote]

Rian, All,

I knocked this one out. Review at your leisure - https://github.com/meshery/meshery/pull/16688

- Lee