S3 Bucket limit produces unhelpfull error on amplify init or push

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

v16.17.0

### Amplify CLI Version

10.3.1

### What operating system are you using?

Mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

N/A

### Amplify Categories

Not applicable

### Amplify Commands

init

### Describe the bug

When the S3 bucket quota has been reached in an account, attempting to run `amplify init` or `amplify push` results in an error:
> `Cannot read property 'has' of undefined`


The actual issue when looking at CloudFormation is:
> `You have attempted to create more buckets than allowed (Service: Amazon S3; Status Code: 400; Error Code: TooManyBuckets`

### Expected behavior

It would be helpful to have a clearer error message, mentioning the bucket limit.

### Reproduction steps

1. Reach the limit of S3 buckets in account
2. Attempt to `amplify init`

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_