Enter fires before Command Palette finishes processing input

### Description of the new feature / enhancement

If I type fast and my command palette hasn't finished the search before I press Enter, then it performs the Enter action immediately without waiting for the search to finish.
I have to type quite fast for it but most of the time it just opens "Search apps" which ist he first option on a freshly opened command palette.

Would be great if the Enter action would wait if there was prior input which is still being processed.

## Different Approach
I use Vivaldi as a browser which has a nice feature for bookmarks,
you can assign aliases to bookmarks and there is a setting for the quick actions to automatically open bookmarks if you enter the exact name of the bookmark.
So the flow would be: Shortcut for quick action -> "risa" -> opens bookmark in new tab.
This totally saves the need to press Enter.

## Considerations
I can see that this might make sense to be an option, as this change could lead to people running commands / applications that they did not intent because they didn't get a visual representation of what will be run after the search finishes.

### Scenario when this would be used?

Quickly opening a shortcut or application.
E.g: the name of my shortcut is "risa", I hit the shortcut to open palette, then in one continuous motion type "risa[Enter]"

### Supporting information

_No response_

Start by locating the command palette's input-processing and Enter-action handling. Reproduce the fast typing sequence described in the issue, then trace how pending search work and Enter are ordered. Done means Enter waits for prior input processing and the resulting action is correct, with coverage for the rapid-input scenario.

Written by the indexing model from the issue text.