Rate-limited pushing to multiple environments at same time

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d2043y24tqcg54

### Region

us-east-2

### Amplify Hosting feature

Backend builds

### Describe the bug

We are a team all using amplify, and our env has several lambdas, models, etc. We have a production env, testing, and then each team member has their own sandbox. Whenever we have multiple environments being pushed to at the same time, the build fails with an error about rate limiting. I thought this would be a quota we could increase, but based on what AWS support is telling me it is not.

From what they told me, the issue is https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DescribeStacks.html

This API call gets throttled with too many concurrent builds.

I'd like to request the ability to increase this service quota to better support teams using Amplify.

### Expected behavior

Should be able to request a service quota increase.

### Reproduction steps

1. Create multiple env setup for amplify project (preferably with large amounts of data to push)
2. Kick off pushes on multiple envs either with CI/CD or amplify push
3. See failures

```
originalError: {
[0m message: 'Rate exceeded',
[0m code: 'Throttling',
[0m time: 2022-05-11T19:21:27.769Z,
[0m requestId: '7e7e4d30-2d5d-4cfc-8c6f-ce4f8cc0a7e9'
[0m },
```

### Build Settings

_No response_

### Additional information

_No response_

The issue names no repository files or tests. Start by reproducing concurrent `amplify push` or CI/CD deployments across multiple environments and inspect the AWS CloudFormation `DescribeStacks` throttling described in the report. Done means establishing a supported way to request or handle the required quota increase.

Written by the indexing model from the issue text.