Unable to amplify mock if developer opted to not make changes to backend during initial amplify pull

### 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/master/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?

yarn

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

_No response_

### Amplify CLI Version

7.6.12

### What operating system are you using?

n/a

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

No manual changes made

### Amplify Categories

function, api

### Amplify Commands

Not applicable

### Describe the bug

Amplify Command: mock (option isn't in dropdown)

Running `amplify mock` fails if the developer selected NO to modifications on backend on initial amplify pull

### Expected behavior

running amplify mock api should work

### Reproduction steps

1. run amplify pull initially
2. select No for do you plan on modifying this backend
3. run amplify mock api
4. failure

### GraphQL schema(s)

_No response_

### Log output

_No response_

### Additional information

_No response_