Imprecision in `multipass help find` message

[ricab]

$ multipass help find
Usage: multipass find [options] [<remote:>][<string>]
Lists available images matching <string> for creating instances from.
With no search string, lists all aliases for supported Ubuntu releases.

Options:
  -h, --help     Display this help
  -v, --verbose  Increase logging verbosity, repeat up to three times for more
                 detail

Arguments:
  string         An optional value to search for in [<remote:>]<string> format,
                 where <remote> can be either ‘release’ or ‘daily’. If <remote>
                 is omitted, it will search ‘release‘ first, and if no matches
                 are found, it will then search ‘daily‘. <string> can be a
                 partial image hash or an Ubuntu release version, codename or
                 alias.

multipass find snapcraft: is a valid command, so the help message for the argument should not limit remotes to release and daily. Perhaps adding snapcraft to the message is enough for now.

Additionally, there should be brackets around <string> in [<remote:>]<string> (as is already the case in the "usage" message.

[ricab]

Perhaps adding snapcraft to the msg would be enough for now. However, future remote addition/removal would make the message outdated again.

To streamline things, if we find it would make sense to have a way to retrieve available remotes — like a slightly different find output (rather than a new command) — that could be tracked in a separate issue.

[ricab]

@Saviq @townsend2010

I agree the best would be pointing to the output of find for the remotes, but is the current format appropriate for that?

[townsend2010]

I think find itself needs some work. It has been pointed out before that the find help is not clear and neither is the output. We should really think about what we want to accomplish with find, like do we want an option to only list remotes (like lxc remote list)? Also, I think the help should not mention any particular remote names since these may change or there are more defined than what the help indicates.

Also, output is clunky, as mentioned in #530.

[Sploder12]

The output format still has the issues described but it is unclear what direction we want to take with this