Organize the list of tasks for easy upgrade vs advanced

[DivergentEuropeans]

First, to begin zwe upgrade epic, we need a prioritized list of tasks a user needs to do for the easiest upgrade vs more required user run tasks:

• A version upgrade, with a different run-time directory and a different Zowe configuration YAML - easiest We don't need to rerun zwe install, we don't need to change our existing DS

• Most customers will upgrade Zowe through SMP/e where they will be re-running zwe install (possibly most common?)

• ???

Think about edgecases for what users want to upgrade, think about the type of user, and format this list preferably into tiers of upgrade, where each tier could be added to be handled by the future zwe upgrade

[1000TurquoisePogs]

SMPE does zwe install in the pipeline rather than having the user do it as in the pax, i believe, so there is no avoiding it? so i guess upgrade is really zwe install + zwe upgrade where zwe upgrade replaces zwe init and maybe, also does other things. in that case, is zwe upgrade the most intuitive name? is there an alternative?