Amplify pull headless with studio disabled causes fetching updates state

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

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

When pulling a Studio enabled backend down the disabling studio and running another headless pull causes the env to stay in fetching updates to backend env state. The CLI prompt asks for auth method, after selection the cli stays in the fetching state.

Workaround: run `amplify configure project` then reselect the profile. The run pull again, this will work as expected.

### Expected behavior

Correctly pull env with studio enabled

### Reproduction steps

1. create a app with few resources such as auth, storage, api etc
2. enable studio
3. pull down the app using headless cli command
4. disable studio
5. run headless pull again
6. observe that the CLI will ask for auth
```
Select the authentication method you want to use:
```
7. I selected profile
observe the cli stays in
```
? Select the authentication method you want to use: AWS profile
⠋ Fetching updates to backend environment: dev from the cloud.? Select the authentication method you want to use: (Use arrow keys)
❯ AWS profile
⠸ Fetching updates to backend environment: dev from the cloud.
```
wait for couple of minutes observe no change

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

Reproduce the sequence using headless `amplify pull`: enable Studio, pull, disable Studio, then pull again and select AWS profile. Compare this with the documented workaround, `amplify configure project` followed by another pull. Done means the second headless pull completes instead of remaining in “Fetching updates to backend environment”.

Written by the indexing model from the issue text.