rerunning pull on a modifiable no to project throws identity pool error for studio creds

### How did you install the Amplify CLI?

npm

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

_No response_

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

### Describe the bug

On studio disabled project, running `amplify pull --appId ` and selecting `no` and rerunning the command throws

```
🛑 Failed to fetch Amplify Studio credentials
IdentityPool 'us-east-1:64892712-fc0b-484e-9d81-72ea310aef3c' not found.
```

this does not occur on a application that did not have studio enabled in the first place. rerunning the command throws no errors

### Expected behavior

not look for studio auth if studio is disabled

### Reproduction steps

1. create a new application on AWS console
2. disable studio
3. create empty folder locally
4. run `amplify pull --appId ` with the app-id filled in. select `no` for allow modifying backend
5. rerun the pull command -> see error
6. try with non studio application, no errors

### 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 with the `amplify pull --appId ` flow and reproduce the second run after selecting no for backend modification on a project with Studio disabled. Trace why the rerun fetches Studio credentials and add regression coverage showing that a disabled Studio project does not look up Studio authentication or fail with an identity-pool error.

Written by the indexing model from the issue text.