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/formatFieldMetadataItemInput.ts

@@ -32,14 +32,14 @@ export const formatFieldMetadataItemInput = (
     const defaultOptions = options?.filter((option) => option.isDefault);
     if (isDefined(defaultOptions)) {
       defaultValue = defaultOptions.map(
-        (defaultOption) => `'${getOptionValueFromLabel(defaultOption.label)}'`,
+        (defaultOption) => `${getOptionValueFromLabel(defaultOption.label)}`,
       );
     }
   }
   if (input.type === FieldMetadataType.Select) {
     const defaultOption = options?.find((option) => option.isDefault);
     defaultValue = isDefined(defaultOption)
-      ? `'${getOptionValueFromLabel(defaultOption.label)}'`
+      ? `${getOptionValueFromLabel(defaultOption.label)}`
       : undefined;
   }