CLI: ability to easily switch between different metadata and config

[barchetta]

Currently the CLI provides the --url option to select different meta-data to run against. A common example of this is to test the archetypes generated in the Helidon build which you do using:

--reset --url file://${HELIDON_WS}/archetypes/helidon/target/cli-data

In order to support other uses of the CLI we should consider making this capability more user friendly. The scenario is this:

I have a team that is using Helidon. I want to provide a zip of a development environment for the team. In the zip I want to include the Helidon CLI and some archetypes used by the CLI that are specific to my team. When I unzip the zip in the filesystem and run the CLI contained in it I want it to pick up the archetypes defined in the filesystem. I also want to version these archetypes based on my version, and not the Helidon version.

This requires the following enhancements:

1. A new concept similar to a git "remote". This is an enhancement to the --url option wheret here is a name and a URL.
2. The ability to manage remotes in the CLI configuration, so I can define a new remote and specify the default remote
3. The ability to tier the CLI configuration and add the concept of the installed configuration, so that the cli knows to look for configuration in the installation directory
4. Don't assume the archetype version and the Helidon version are the same (not sure if we do or not)

[romain-grecourt]

See also #408