exiting `amplify console` with ctrl+c errors with `undefined`

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

pnpm

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

18

### Amplify CLI Version

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

n/a

### Amplify Categories

Not applicable

### Amplify Commands

Not applicable

### Describe the bug

```
➜ amplify console
✖ Which site do you want to open? · Amplify Studio
🛑 undefined
```

### Expected behavior

cli exits without error

### Reproduction steps

1. `amplify console`
2. ctrl+c at prompt
3. observe error

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

Start by running `amplify console` with Amplify CLI 10.5.0 on macOS and press Ctrl+C at the site-selection prompt. Trace the `amplify console` command's cancellation path and its error output; done means Ctrl+C exits without printing `undefined`, with a regression test if the command's existing tests provide a suitable place.

Written by the indexing model from the issue text.