resource overrides with yarn3/yarn2

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

12.4.0

### What operating system are you using?

macos

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

no

### Describe the bug

When we have yarn3 installed locally, then try to add override to a category the CLI fails similar to https://github.com/aws-amplify/amplify-cli/issues/13178.

But adding `--debug` to the override command when failing causes the override file to get created.

similar behaviour with yarn2

### Expected behavior

consistent behavior

### Reproduction steps

1. yarn set version stable
2. yarn install
3. amplify api override -> observe error
4. amplify api override -> no error

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