`limactl menu` TUI

https://github.com/afbjorklund/lima-tui or something similar should be integrated to Lima as a CLI plugin
`limactl-menu`.

https://github.com/lima-vm/lima/blob/596bc53e45ff761563ecc0fa33dfe3feb469ae18/Makefile#L319

The plugin will be runnable as `limactl menu`.
Probably `limactl` w/o the subcommand may invoke the plugin by default when the plugin is installed.

Note: if we are going to adopt https://github.com/afbjorklund/lima-tui , it has to be cleaned up first to remove the code that does not relate to Lima.

- - -

> Pterm uses the "inline" style of interface, which for Lima is a feature and not really a shortcoming.
>
> So that makes it a nice replacement for survey, and has more similar widgets: see the [_examples](https://github.com/pterm/pterm/tree/master/_examples)
>
> ----
>
> If making a whole application with menus and such, then I think using [tview](https://github.com/rivo/tview) is a better match.
>
> See https://github.com/afbjorklund/lima-tui for PoC - it is mostly a ripoff of lazyssh and lazydocker
>
>
>
>

> This feature is only about replacing survey for what is in the Lima CLI - not the Lima TUI (or GUI)

_Originally posted by @afbjorklund in [#1881](https://github.com/lima-vm/lima/issues/1881#issuecomment-4363401849)_

Start with the Makefile entry around line 319 and the existing limactl command entry point. Review the proposed lima-tui integration and its unrelated code, along with the discussion of pterm and tview, before deciding the plugin boundary. Done means a cleaned-up CLI plugin runs as `limactl menu`; default invocation remains an open design question.

Written by the indexing model from the issue text.