Update 1.10 enterprise upgrade docs.

[mkeeler]

I think I have some overall structure in place but I found out that our general upgrade guide is kind of lacking. It goes over how to do an in place upgrade of OSS but doesn't cover autopilot assisted upgrades, client upgrades or snapshot agent upgrades.

Additionally, my plan was to have version specific upgrade paths in the guide. However I realized that clusters could have mixed versions and then specifying that would get way too complicated vs just saying that at each step all servers, or clients or snapshot agents needed to be upgraded to the latest in either the 1.8.x or 1.9.x series.

There are a bunch of vague steps in the 1.10 upgrade guide that I want to fill in with more info but was hoping for others opinions on how to proceed. Originally I was going to link out to the general upgrade process but that just covers upgrading the servers using an in-place upgrade strategy. This didn't seem great as I expect many enterprise users are going to use automated upgrades. So basically what would others like to see at these locations. It feels like we should have other documentation around the various scenarios but in the absence of that I am not sure what would be best in these docs.

[hashicorp-ci]

🤔 This PR has changes in the website/ directory but does not have a type/docs-cherrypick label. If the changes are for the next version, this can be ignored. If they are updates to current docs, attach the label to auto cherrypick to the stable-website branch after merging.

[mkeeler]

The current 1.10 upgrade page instructions are live here: https://consul-7a2vaizou-hashicorp.vercel.app/docs/upgrading/instructions/upgrade-to-1-10-x

[banks]

Looks super close actually, these are not major changes but I think a few might be important in keeping things as clear as possible!

[preetapan]

Added some comments. To your question around :

There are a bunch of vague steps in the 1.10 upgrade guide that I want to fill in with more info but was hoping for others opinions on how to proceed. Originally I was going to link out to the general upgrade process but that just covers upgrading the servers using an in-place upgrade strategy. This didn't seem great as I expect many enterprise users are going to use automated upgrades. So basically what would others like to see at these locations. It feels like we should have other documentation around the various scenarios but in the absence of that I am not sure what would be best in these docs.

IMO, we have existing docs around in place upgrades vs autopilot upgrades already. So I'd add a generic sentence before the detailed steps in the preceding paragraph, something like "These instructions require licensing related configuration changes needed to upgrade to 1.10, and also require intermediate upgrade versions to ensure forward compatibility. We recommend using your existing upgrade strategies such as <link to autopilot upgrade guide> during this multi stage process"

[mkeeler]

Note that this link will be broken until we release 1.10

[thisisnotashwin]

thanks Matt!!

[hc-github-team-consul-core]

🍒 If backport labels were added before merging, cherry-picking will start automatically.

To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/393397.

[hc-github-team-consul-core]

🍒✅ Cherry pick of commit 76857dd onto release/1.10.x succeeded!