Implement eager load relations on graphqlQueries

[charlesBochet]

In this PR, I'm refactoring the way graphql queries are built from objectMetadata in the different hooks:

• useGenerateFindOneRecordQuery
• useGenerateFindManyRecordQuery
• ...

All these hooks were querying useMapFieldMetadataToGraphQLQuery

1. converting useMapFieldMetadataToGraphQLQuery hook to an utils mapFieldMetadataToGraphQLQuery to avoid nesting loop loading of objectMetadataItems (~30us x 200 = 6ms) for a classic object with nesting 2.

2. introducing mapObjectMetadataToGraphQLQuery to refactor mapping over object that was implemented ~10 times into one place

3. introducing shouldFieldBeQueried

4. introducing the possibility to query only a selected number of relations / fields
   ex:

const res = mapFieldMetadataToGraphQLQuery({
      objectMetadataItems: mockObjectMetadataItems,
      relationFieldDepth: 2,
      relationFieldEagerLoad: { accountOwner: true, people: true },
      field: CompanyFieldMetadataItem
    });

This can be nested as far as we want

5. Adding tests

6. Fine tuning depths in the code base to lower the calls

Next steps:

• on Tasks Page, load all activityTargets at once (there are many many calls being performed currenty)
• on Index Pages, only include the relations that are needed in the table / board based on ViewFields
• (also double check what's happening to an exisitng object in the cache, when make a new graphql query without some relations. we should keep the information we already have)