STCLI-279 remove configuration warnings for '--federate' flag

[JohnC-80]

This PR removes the warnings about building/serving without a config file if the --federate command is used, where configs are optional.

It also adds some more context-specific messaging about where the command is executed - in the ui-module or host app space.

[github-actions]

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit dc41de9. ± Comparison against base commit b138c47.

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

With further testing, I realzied stripes-webpack no longer starts the local registry service when stripes-cli is called like build --federate instead of build path/to/stripes.config.js --federate.

[JohnC-80]

@zburke - we don't automatically start the local registry server with build - we never have The POC may have done this - but is it really necessary? The intent with build is to take the output and push it somewhere else, not to develop locally. If starting the registry server is something desired with build, it will need a separate option. serve on the other hand, will start the registry, as it's meant for local development.

[zburke]

Whoops, typo: you're right that we don't (and shouldn't) start the local registry on build. The problem is that I don't see the registry starting when serving a platform like ```
yarn stripes serve --federate

The local registry only starts for me when I pass in a config file like

yarn stripes serve ./stripes.config.js.local --federate