feat(shortcuts)!: remove setRawMode

[bluwy]

Description

Remove setRawMode for shortcuts to prevent the following caveats:

1. Exit code is always 1. Why: fix(cli): exit 1 on ctrl+c #11563
2. Suspending in background mode does not always work. Issue: suspend is not working in dev mode #11300
3. Vite manually handles Ctrl-C and Ctrl-D, and blocks OS-specific shortcuts. Issue: suspend is not working in dev mode #11300
4. Swallows user input. Can't enter-enter-enter to create a virtual separation in the CLI.

For the above reasons, it's best to not use setRawMode and let the OS and Node.js handle the inputs as usual. The downside is that every shortcuts needs to be followed with an Enter press to execute it (creates a new line to read the input).

Close #11300
Close #14319
Close #11418

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[ArnaudBarre]

This also added benefit is that shortcut can be to chars long to choose a random letter if the first letter of a new aciton is already taken

[bluwy]

Through some discussion, it's better to get this correct instead to avoid the potential issues. Vite's dev server is commonly used to pair with other processes and it would not be great if there's subtle issues with those.

I've made a poll (albeit only a small sample size) at https://twitter.com/bluwyoo/status/1704408350656782430 and https://elk.zone/m.webtoo.ls/@bluwy/111096467000284501. The rough average is that:

• 57% of users are ok with this change
• 22% of users are ok but slightly annoyed
• 21% of users dislike this change

While it's still a significant portion of users who oppose this, the majority are still able to accept this. So we're going ahead with this change.

[WORMSS]

Is there any way to get the original behaviour back? It is highly annoying.