permissions boundary update does not actually update and causes next push to hang

### How did you install the Amplify CLI?

npm

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

16

### Amplify CLI Version

10.7.3

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

### Describe the bug

Running `amplify env update --permissions-boundary` causes the next push to hang and the updated value is overwritten with the previous value

### Expected behavior

permissions boundary update should be retained and applied on the next push

### Reproduction steps

1. `amplify init --permissions-boundary arn:aws:iam::aws:policy/AmazonS3FullAccess`
2. `amplify env update --permissions-boundary arn:aws:iam::aws:policy/AmazonDynamoDBFullAccess`
3. `amplify push --force`

Observe that the push hangs and permissions boundary value in `team-provider-info.json` is reverted to S3FullAccess

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

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

Start by reproducing the issue with the listed amplify init, amplify env update, and amplify push commands, then trace how the permissions boundary is stored in team-provider-info.json. Check that the updated boundary is retained and applied during the next push without hanging.

Written by the indexing model from the issue text.