feat: new relation sync-metadata, twenty-orm, create/update (#10217)

Fix
https://github.com/twentyhq/core-team-issues/issues/330#issue-2827026606
and
https://github.com/twentyhq/core-team-issues/issues/327#issue-2827001814

What this PR does when `isNewRelationEnabled` is set to `true`:
- [x] Drop the creation of the  foreign key as a `FieldMetadata`
- [x] Stop creating `RelationMetadata`
- [x] Properly fill `FieldMetadata` of type `RELATION` during the sync
command
- [x] Use new relation settings in TwentyORM
- [x] Properly create `FieldMetadata` relations when we create a new
object
- [x] Handle `database:reset` with new relations

---------

Co-authored-by: Charles Bochet <charles@twenty.com>
Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com>

packages/twenty-server/src/engine/metadata-modules/object-metadata/utils/build-migrations-for-custom-object-relations.util.ts

@@ -23,6 +23,7 @@ export const buildMigrationsForCustomObjectRelations = (
         columns: [
           {
             action: WorkspaceMigrationColumnActionType.CREATE,
+            // TODO: When we get rid of this and use the sync metadata, columnName must be based on the joinColumnName from the field metadata settings
             columnName: computeColumnName(createdObjectMetadata.nameSingular, {
               isForeignKey: true,
             }),
@@ -38,6 +39,7 @@ export const buildMigrationsForCustomObjectRelations = (
         columns: [
           {
             action: WorkspaceMigrationColumnActionType.CREATE_FOREIGN_KEY,
+            // TODO: When we get rid of this and use the sync metadata, columnName must be based on the joinColumnName from the field metadata settings
             columnName: computeColumnName(createdObjectMetadata.nameSingular, {
               isForeignKey: true,
             }),