Upgrading Jira Data Center on AWS should not tell customers to scale up the cluster back to the existing number of nodes at once

Issue Summary

https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-on-aws-945105105.html is missing potentially critical step that could lead to higher customer friction, i.e. L1s and L2s created for support

Step 3: Scale up the number of application nodes implies that it's OK to scale up the number of nodes back to the original number at once. This is very risky for customers running JIRA below version 9.1.0 due to this bug:
https://jira.atlassian.com/browse/JRASERVER-72125 where by we state that it was admin's responsibility to to ensure only one node starts at a time and that all nodes in the cluster are healthy, so that each of them can provide a healthy snapshot

Expected Results

We need to state that customers should add one node at a time and wait for it to be fully started before deploying another node.

Steps to Reproduce

Open the linked article

Actual Results

We simply state that customers can scale up the cluster back to the original number of nodes which can lead to all sorts of issues like:
https://jira.atlassian.com/browse/JRASERVER-66635
https://jira.atlassian.com/browse/JRASERVER-72125

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available