Command Palette: Make "Alias" feature for pinned apps a bit more obvious

### Description of the new feature / enhancement

When searching for tools and such, I find that the less I have to type, the better. Also, sometimes if there are multiple results for a specific search because the results all have the same sequence of characters or something (e.g. `CMD` (command prompt) and `Git CMD`), but the one you want is not prioritized.

Here's my proposal: A keyword lookup feature. Basically, the user creates a list of "keyword shortcuts." Each of these shortcuts consists of a keyword (e.g. `vsc`) and points to an action of the user's choice, such as a program. For example, by typing `/as`, I could immediately be given the result of `Android Studio`. Or, by typing `/cmd`, I would be given the result for Command Prompt. Even if there were 5 other programs with the name CMD in them, the Command Prompt would be the first on the list.

The advantage: Rather than having to type the entire name of the program, if it's one you visit frequently (but you don't want to pin them all to the homepage), you can type in a specific user identifier that gives you an immediate result. This could potentially save people like me loads of time.

### Scenario when this would be used?

I'm not that fast (or even that good) of a typist. If I have to type the words `Android Studio`, it's a bit slower. If I could just type `/as` and immediately get Android Studio as a result, then that shaves off time. If I have Visual Studio Code and Visual Studio Community installed, and I want Visual Studio Code, typing `/vsc` would give me Visual Studio Code at the very top of the list.

### Supporting information

_No response_

Start by reviewing the existing Command Palette behavior for pinned apps and the current Alias feature, then determine how the proposed keyword shortcuts should be created, displayed, and prioritized. Define the user-facing interaction and acceptance criteria for aliases such as /as and /cmd; the issue names no files or tests, so repository exploration is required before implementation.

Written by the indexing model from the issue text.