Users do not automatically get new or changed config values upon upgrade

[1000TurquoisePogs]

Because zowe's server config is based upon starting with an example config file, and editing it, it is likely that users will create a working config file, and then not update it with every upgrade, even though they should because new zowe versions can come with new features and changes in desired defaults.

I say "desired defaults" because, since there isnt a default file, just an example file, there really isn't a default config.

We should move from an example-based config to a default-based config, using the multi-yaml feature here https://docs.zowe.org/stable/user-guide/configmgr-using/ such that the first file in the list can be zowe's default file, so that users will pick up new values & changes in defaults over time.

[1000TurquoisePogs]

for the idea of a defaults-based yaml, i started some work here https://github.com/zowe/zowe-install-packaging/pull/3356 but would be happy if others picked it up or gave feedback, because it's something i was only working on with spare time at the moment.