feat(cli): Fix erroneous subcommand as a run tentative

[xdoardo]

This small PR introduces a mechanism that, in case the CLI parser fails to parse the command correctly, tries to dynamically match the first argument given to the CLI against the names of available subcommands before trying to interpret it as the name of a package to run.

For example, this helps avoiding situations such as

$ wasmer deploy my-app
<tries to *run* the package `deploy`>

With this patch, it will instead result in:

$ wasmer deploy test 
error: unexpected argument 'test' found

Usage: wasmer deploy [OPTIONS]

For more information, try '--help'.

I don't think that the overhead of this patch will be unbearable, but another, lighter possibility to avoid this problem is to make it so that the wasmer_config::package::PackageSource struct does not allow non-namespaced named packages, if viable (e.g. namespace/name@version is ok, namespace/name is ok, name@version is not)