Refactor RecordSingleSelect and RecordMultiSelect to be synchronous

[charlesBochet]

Context

We are experiencing a lot of re-rendering / flash on MultiRecordSelect / SingleRecordSelect / RelationPicker.

This PR is a first step to refactor this components

Scope

Only move files to uniformize and prepare for the upcoming refactoring

Vision

• SingleRecordPicker
• MultipleRecordPicker
• sharing RecordPicker tooling (RecordPickerComponentInstanceContext, searchState)

Used in other areas:

• RelationPicker (which is actually only a subcomponent of RelationToOneFieldInput)
• RelationFromManyFieldInput
• WorkflowRelationFieldInput
• etc.

• remove all effects
• migrate to the latest APIs
• make a pass on re-renders to remove them completely (we likely need to use a bit more familyStates here)

[greptile-apps]

PR Summary

This PR optimizes the MultiRecordSelect component by improving click-outside handling and reducing unnecessary re-renders.

• Replaced MultipleObjectRecordOnClickOutsideEffect with direct useListenClickOutside hook implementation in packages/twenty-front/src/modules/object-record/relation-picker/components/MultiRecordSelect.tsx
• Removed unnecessary useEffect for hotkey scope setting that was causing re-renders
• Refactored Escape key handler into a consolidated handleSubmit function
• Simplified component structure by removing wrapper fragment
• Improved performance by reducing state changes and component nesting

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}