Amplify CLI command to allow backend update

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

_No response_

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

_No response_

### Amplify CLI Version

9.2.1

### What operating system are you using?

Windows

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

NO

### Amplify Categories

Not applicable

### Amplify Commands

pull

### Describe the bug

On pulling a backend from Amplify console, the prompt allows us to select if we plan to modify a backend. If we select `no`, but later in point of time decide we need to make some modifications amplify will throw `unable to find amplify-meta.json` error.

The workarounds are.
1. Delete the Amplify folder and pull the Amplify backend again, but this time selecting `yes` when prompted to allow modify backend.
2. change the `noUpdateBackend` attribute to false in `amplify/.config/local-env-info.json` then run `amplify pull`. While selecting `yes` when prompted to allow modify backend.

### Expected behavior

Amplify CLI command should allow users to modify the backend.

### Reproduction steps

1. `amplify pull `
2. select `no`

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