[POC] add graphql query runner (#6747)

## Context
The goal is to replace pg_graphql with our own ORM wrapper (TwentyORM).
This PR tries to add some parsing logic to convert graphql requests to
send to the ORM to replace pg_graphql implementation.

---------

Co-authored-by: Charles Bochet <charles@twenty.com>

packages/twenty-server/src/engine/twenty-orm/utils/determine-relation-details.util.ts

@@ -21,7 +21,10 @@ export async function determineRelationDetails(
   let fromObjectMetadata: ObjectMetadataEntity | undefined =
     fieldMetadata.object;
   let toObjectMetadata: ObjectMetadataEntity | undefined =
-    relationMetadata.toObjectMetadata;
+    objectMetadataCollection.find(
+      (objectMetadata) =>
+        objectMetadata.id === relationMetadata.toObjectMetadataId,
+    );
 
   // RelationMetadata always store the relation from the perspective of the `from` object, MANY_TO_ONE relations are not stored yet
   if (relationType === 'many-to-one') {
@@ -37,6 +40,16 @@ export async function determineRelationDetails(
     throw new Error('Object metadata not found');
   }
 
+  const toFieldMetadata = toObjectMetadata.fields.find((field) =>
+    relationType === 'many-to-one'
+      ? field.id === relationMetadata.fromFieldMetadataId
+      : field.id === relationMetadata.toFieldMetadataId,
+  );
+
+  if (!toFieldMetadata) {
+    throw new Error('To field metadata not found');
+  }
+
   // TODO: Support many to many relations
   if (relationType === 'many-to-many') {
     throw new Error('Many to many relations are not supported yet');
@@ -45,7 +58,7 @@ export async function determineRelationDetails(
   return {
     relationType,
     target: toObjectMetadata.nameSingular,
-    inverseSide: fromObjectMetadata.nameSingular,
+    inverseSide: toFieldMetadata.name,
     joinColumn:
       // TODO: This will work for now but we need to handle this better in the future for custom names on the join column
       relationType === 'many-to-one' ||