Move ctp connect to ctp connector install

[tnthornton]

Description of your changes

This PR shuffles the subcommands around a little. This is in anticipation of some reworking for ctp connect.

This changeset builds on #388. #388 should be merged/reviewed prior to this PR.

I have:

• Read and followed Upbound's contribution process.
• Run make reviewable to ensure this PR is ready for review.

How has this code been tested

./_output/bin/darwin_arm64/up ctp --help
Usage: up controlplane (ctp) <command>

Interact with control planes.

Flags:
  -h, --help                         Show context-sensitive help.
      --format="default"             Format for get/list commands. Can be: json, yaml, default
  -v, --version                      Print version and exit.
  -q, --quiet                        Suppress all output.
      --pretty                       Pretty print output.

      --domain=https://upbound.io    Root Upbound domain ($UP_DOMAIN).
      --profile=STRING               Profile used to execute command ($UP_PROFILE).
  -a, --account=STRING               Account used to execute command ($UP_ACCOUNT).
      --insecure-skip-tls-verify     [INSECURE] Skip verifying TLS certificates
                                     ($UP_INSECURE_SKIP_TLS_VERIFY).
  -d, --debug=INT                    [INSECURE] Run with debug logging. Repeat to increase verbosity.
                                     Output might contain confidential data like tokens ($UP_DEBUG).

Commands:
  controlplane (ctp) create           Create a managed control plane.
  controlplane (ctp) delete           Delete a control plane.
  controlplane (ctp) list             List control planes for the account.
  controlplane (ctp) get              Get a single control plane.
  controlplane (ctp) connector        Connect an App Cluster to a managed control plane.
  controlplane (ctp) configuration    Manage Configurations.
  controlplane (ctp) provider         Manage Providers.
  controlplane (ctp) pull-secret      Manage package pull secrets.
  controlplane (ctp) kubeconfig       Manage control plane kubeconfig data.

./_output/bin/darwin_arm64/up ctp connector --help
Usage: up controlplane (ctp) connector <command>

Connect an App Cluster to a managed control plane.

Flags:
  -h, --help                         Show context-sensitive help.
      --format="default"             Format for get/list commands. Can be: json, yaml, default
  -v, --version                      Print version and exit.
  -q, --quiet                        Suppress all output.
      --pretty                       Pretty print output.

      --domain=https://upbound.io    Root Upbound domain ($UP_DOMAIN).
      --profile=STRING               Profile used to execute command ($UP_PROFILE).
  -a, --account=STRING               Account used to execute command ($UP_ACCOUNT).
      --insecure-skip-tls-verify     [INSECURE] Skip verifying TLS certificates
                                     ($UP_INSECURE_SKIP_TLS_VERIFY).
  -d, --debug=INT                    [INSECURE] Run with debug logging. Repeat to increase verbosity.
                                     Output might contain confidential data like tokens ($UP_DEBUG).

Commands:
  controlplane (ctp) connector install    Install mcp-connector into an App Cluster.

[AlainRoy]

This is way better than I would have done, had I finished it. It looks great, and I like the approach to having a unified response for the two kinds of control planes.

My only comments are nits -- very small.

One question: The description for the PR sounds much more limited than what is actually here. Is the description wrong, or did you not intend to include everything in this PR? I'm okay with it all being included, just making sure it's what you expect.

Other than that last concerns (about the description matching the contents), I'm happy and will pre-emptively approve, assuming you'll fix the description if appropriate.

[AlainRoy]

Wait, I looked that the PRs in the wrong order: this overlaps #388. I'm guessing this PR needs to be updated? Maybe you should ignore my approval there.

[tnthornton]

Wait, I looked that the PRs in the wrong order: this overlaps #388. I'm guessing this PR needs to be updated? Maybe you should ignore my approval there.

Ya, this is branched from #388 and builds on that guy. I called that out in the description too 👍 . I'm guessing this is the reason for this comment:

One question: The description for the PR sounds much more limited than what is actually here. Is the description wrong, or did you not intend to include everything in this PR? I'm okay with it all being included, just making sure it's what you expect.

?

[AlainRoy]

Wait, I looked that the PRs in the wrong order: this overlaps #388. I'm guessing this PR needs to be updated? Maybe you should ignore my approval there.

Ya, this is branched from #388 and builds on that guy. I called that out in the description too 👍 . I'm guessing this is the reason for this comment:

One question: The description for the PR sounds much more limited than what is actually here. Is the description wrong, or did you not intend to include everything in this PR? I'm okay with it all being included, just making sure it's what you expect.

?

Yeah, I just got confused since it's awaiting the merge, so there was more code. It all looks good though.