Add composite Emails field and forbid creation of Email field type (#6689)

### Description

1. 
   - We are introducing new field type(Emails)


   - We are Forbiding creation of Email field


   - We Added support for filtering and sorting on Emails field


- We are using the same display mode as used on the Links field type
(chips), check the Domain field of the Company object


   - We are also using the same logic of the link when editing the field

   \
   How To Test\
   Follow the below steps for testing locally:\
   1. Checkout to TWENTY-6261\
2. Reset database using "npx nx database:reset twenty-server" command\
   3. Run both the backend and frontend app\
4. Go to Settings/Data model and choose one of the standard objects like
people\
   5. Click on Add Field button and choose Emails as the field type

   \
   ### Refs

   #6261\
   \
   ### Demo

    \

<https://www.loom.com/share/22979acac8134ed390fef93cc56fe07c?sid=adafba94-840d-4f01-872c-dc9ec256d987>

Co-authored-by: gitstart-twenty <gitstart-twenty@users.noreply.github.com>

packages/twenty-server/src/engine/core-modules/open-api/utils/__tests__/components.utils.spec.ts

@@ -147,6 +147,17 @@ describe('computeSchemaComponents', () => {
             },
             type: 'object',
           },
+          fieldEmails: {
+            properties: {
+              primaryEmail: {
+                type: 'string',
+              },
+              additionalEmails: {
+                type: 'object',
+              },
+            },
+            type: 'object',
+          },
         },
       },
       'ObjectName with Relations': {

packages/twenty-server/src/engine/core-modules/open-api/utils/components.utils.ts

@@ -72,6 +72,7 @@ const getSchemaComponentsProperties = (
       case FieldMetadataType.FULL_NAME:
       case FieldMetadataType.ADDRESS:
       case FieldMetadataType.ACTOR:
+      case FieldMetadataType.EMAILS:
         itemProperty = {
           type: 'object',
           properties: compositeTypeDefinitions