Fix enum defaultValue issues (#5307)

This PR fixes several issues:
- enum naming should be: {tableName}_{fieldName}_enum and respecting the
case
- defaultValue format handled in the FE should respect the one in the BE

In my opinion we should refactor the defaultValue:
- we should respect backend format: "'myDefault'" for constant default
and "0" for float, "now" for expressions, "true" for booleans. we can
rename it to defaultValueExpression if it is more clear but we should
not maintain a parallel system
- we should deprecate option: isDefaultValue which is confusing
- we should re-work backend to have a more unified approach between
fields and avoid having if everywhere about select, multiselect, and
currency cases. one unified "computeDefaultValue" function should do the
job

What is still broken:
- currency default Value on creation. I think we should do the refactor
first
- select default value edition.
These cases do not break the schema but are ignored currently

packages/twenty-front/src/modules/object-metadata/utils/getDefaultValueForBackend.ts

@@ -1,3 +1,4 @@
+import { CurrencyCode } from '@/object-record/record-field/types/CurrencyCode';
 import { FieldCurrencyValue } from '@/object-record/record-field/types/FieldMetadata';
 import { FieldMetadataType } from '~/generated-metadata/graphql';
 
@@ -9,10 +10,12 @@ export const getDefaultValueForBackend = (
     const currencyDefaultValue = defaultValue as FieldCurrencyValue;
     return {
       amountMicros: currencyDefaultValue.amountMicros,
-      currencyCode: `'${currencyDefaultValue.currencyCode}'` as any,
+      currencyCode: `'${currencyDefaultValue.currencyCode}'` as CurrencyCode,
     } satisfies FieldCurrencyValue;
-  } else if (typeof defaultValue === 'string') {
+  } else if (fieldMetadataType === FieldMetadataType.Select) {
     return `'${defaultValue}'`;
+  } else if (fieldMetadataType === FieldMetadataType.MultiSelect) {
+    return defaultValue.map((value: string) => `'${value}'`);
   }
 
   return defaultValue;