ref(cmdk) jsx powered cmdk

[JonasBa]

Refactor CMDK to a composable JSX approach.

Previously, our CMDK required knowing actions aot and use a hook registration process. We want to move to a fully JSX powered approach and eventually also make actions render to the DOM (this is currently not possible because virtualization is required and the listbox API requires us to specify the full list)

This change brings us half way to being able to power the CMDK UI by converting CMDK registration to JSX.

This enables some interesting patterns where the UI logic can be colocated with the UI as seen here.

The way that this works is through the following mechanisms:

• Collection context responsible for storing nodes and edges (essentially a recursive Context) that we use to maintain a parent<->child mapping.
• A store with a tree(root | undefined) method which will reconstruct the tree on-demand so that callers can have access to the most complete UI at all times

The slots API mentioned above this are used in CMDK as contextual priority slots that will appear as the first descendants of the CMDK action (similar to how priority int value used to work before). CMDK now has two slots, the first one is the global slot where global actions should be registered, the second is the page where broader page specific actions can be registered and the 3rd is the task slot, a slot that is contextual to what the user is doing (e.g. if they are editing a dashboard, saving or starring it might be a task they are currently interested).

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c153ff0. Configure here.}