Failure to clone environment when Notifications category is added

### How did you install the Amplify CLI?

npm

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

v18.15.0

### Amplify CLI Version

12.4.0

### 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.

No manual changes made

### Describe the bug

After adding notifications to environment by `amplify notifications add` using `amplify add env` to clone this env fails.


### Expected behavior

Having notifications/analytics (Pinpoint project added) doesn't affect cloning environment.

### Reproduction steps

1. Create main env and add Auth category.
2. Add notifications category
3. Try to clone this environment

### Project Identifier

75e2f18c9b268cfb1285dcab10f7a0ff

### Log output

```
# Put your logs below this line

```

### Additional information

Cloning environment with following categories: API, Authentication, Functions, Storage works fine.

### Before submitting, please confirm:

- [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.