Action menu refactoring (#11454)

# Description

Closes [#696](https://github.com/twentyhq/core-team-issues/issues/696)

- `useAction` hooks have been removed for all actions
- Every action can now declare a react component
- Some standard action components have been introduced: `Action`,
`ActionLink` and `ActionModal`
- The `ActionDisplay` component uses the new `displayType` prop of the
`ActionMenuContext` to render the right component for the action
according to its container: `ActionButton`, `ActionDropdownItem` or
`ActionListItem`
- The `ActionDisplayer` wraps the action component inside a context
which gives it all the information about the action
-`actionMenuEntriesComponenState` has been removed and now all actions
are computed directly using `useRegisteredAction`
- This computation is done inside `ActionMenuContextProvider` and the
actions are passed inside a context
- `actionMenuType` gives information about the container of the action,
so the action can know wether or not to close this container upon
execution

packages/twenty-front/src/modules/command-menu/pages/search/components/CommandMenuSearchRecordsPage.tsx

@@ -6,7 +6,9 @@ export const CommandMenuSearchRecordsPage = () => {
   const { commandGroups, loading, noResults } = useCommandMenuSearchRecords();
 
   const selectableItemIds = useMemo(() => {
-    return commandGroups.flatMap((group) => group.items).map((item) => item.id);
+    return commandGroups
+      .flatMap((group) => group.items)
+      .map((item) => item.key);
   }, [commandGroups]);
 
   return (