Remove ConfigManager caching capabilities to improve user experience

[jeromy-cannon]

While the caching of the ConfigManager reduces the number of flags that a user has to enter, it also causes a lot of confusion and sometimes doesn't automatically get uncached. Considering our future designs with multi-cluster the caching of these flags needs to be removed. We want the user to either use the prompts or the flags for each command, and the number of commands will be reduced in the future.

Here is a list, although there might be need to be more items that aren't documented:

Tasks

Beta Give feedback

1. update: ConfigManager.constructor, remove 2nd parameter cachedConfigFile
2. update: ConfigManager.applyPrecedence jsdoc refers to cached config
3. update: ConfigManager.update, remove 2nd parameter persist
4. update: ConfigManager.persist
5. remove: ConfigManager.load
6. remove: constants.SOLO_CONFIG_FILE
7. many test cases will need updating and refactoring since they rely upon caching of the flags
8. the workflow that generates the README will need to be updated
9. the README template file may also need to be updated