tctl resource selection ux

[GavinFrazar]

This PR allows users to select resources in tctl [get | edit | rm] for resources of kind db, db_server, kube_cluster, and kube_server using a prefix of the resource name.

Part of the implementation for RFD 129.

Majority of changes were in adding test coverage for these commands.

UX

If the name given by the user matches any resource's name exactly, other resources that match the prefix are ignored, to avoid annoying UX, for example:

## assume there are databases `foo`, `foo-bar`
## this command should select only database `foo`, because it matches exactly, and ignore `foo-bar`.
$ tctl rm db/foo

Additionally, since tctl rm is a destructive action, I decided to make it an error if the given name matches multiple resources at once, which is consistent with how we already allow tctl get <kind> and disallow tctl rm <kind>:

## assume there are databases: `foo`, `foo-bar`
$ tctl rm db/f
ERROR: db/f matches multiple databases as a name prefix:
foo
foo-bar

Use either a full resource name or an unambiguous prefix, for example:
$ tctl rm db/foo-bar

For tctl get and tctl edit, a prefix is allowed to match more than one resource:

## assume there are databases: `foo`, `foo-bar`
$ tctl get db/f
...prints both databases...

Related issue:

• Add ability to differentiate auto-discovered databases #22438

[public-teleport-github-review-bot]

@GavinFrazar See the table below for backport results.

Branch	Result
branch/v13	Failed