[Feature Request] - Allow automatic deployment in StackSets to follow the order of configured regions when deploying new stack instances.

### Name of the resource

Other

### Resource name

CloudFormation StackSets

### Description

When enabling automatic deployment on a StackSet in the management console, you only get options to active/deactivate automatic deployment and account removal behaviour.

When you add stacks to a StackSet, you specify regions and that order of regions will be followed when stack instances are created. With automatic deployment, that order of regions is not followed and a different regions will be selected to start with. This can result in errors if resources in the first region are to be used in other regions.

It would be great for automatic deployment to follow the order of how the present stack instances were deployed based on regions or how the order of regions in the StackSet was configured.

### Other Details

_No response_

Start by reviewing the CloudFormation StackSets automatic deployment behavior described in the issue, including how configured regions and existing stack instance deployment order are selected. Done means automatic deployment follows the StackSet's configured or established region order, preventing dependent resources from starting in the wrong region. No repository files or tests are named.

Written by the indexing model from the issue text.