[Docs] Cleaning up the versions in the upgrade paths. Closes #116223 #116228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Using version attributes in the upgrade paths was resulting in telling people to upgrade to "7.x" and implying that upgrading to GA from a pre-release was ok. (It might technically be okay for Kibana, but it's definitely not supported on the Elasticsearch side & we don't want to encourage people to treat the pre-release versions as steps on their upgrade path.)
This will need another overhaul before 8.1, anyway, so I hardcoded the versions.
You can't actually follow the recommended path just yet, but if people are starting to think about upgrading, we want to get them thinking about the proper order of things.