Setup, Update, and Build SettingsManager can't optimize based on user supplied CLI options because there is no sharing of that back to settings manager

[spbrogan]

In trying to optimize the ci build time more has been identified that can be done if the SettingsManagers know more about what is going to actually build. This means things like individual packages, architectures, and targets. The SettingsManagers must be notified of the CLI settings prior to providing the active scopes or required repos.

A few optimizations that should be supported:

• If a run is not going to build cryptopkg then it might not need the OpenSSL submodule.
  • This means that stuart setup, ci setup, and update needs to optionally be told what package is going to be built so that submodules and dependencies could be managed.
• A run might only want to compile for DEBUG or RELEASE.
  • The Target should be settable on the cli.
• A run might only want to compile/test for a given arch
  • Arch should be settable on the cli

[spbrogan]

resolved by PR #48