Improve performance on metadata computation (#12785)

In this PR:

## Improve recompute metadata cache performance. We are aiming for
~100ms

Deleting relationMetadata table and FKs pointing on it
Fetching indexMetadata and indexFieldMetadata in a separate query as
typeorm is suboptimizing

## Remove caching lock

As recomputing the metadata cache is lighter, we try to stop preventing
multiple concurrent computations. This also simplifies interfaces

## Introduce self recovery mecanisms to recompute cache automatically if
corrupted

Aka getFreshObjectMetadataMaps

## custom object resolver performance improvement:  1sec to 200ms

Double check queries and indexes used while creating a custom object
Remove the queries to db to use the cached objectMetadataMap

## reduce objectMetadataMaps to 500kb
<img width="222" alt="image"
src="https://github.com/user-attachments/assets/2370dc80-49b6-4b63-8d5e-30c5ebdaa062"
/>

We used to stored 3 fieldMetadataMaps (byId, byName, byJoinColumnName).
While this is great for devXP, this is not great for performances.
Using the same mecanisme as for objectMetadataMap: we only keep byIdMap
and introduce two otherMaps to idByName, idByJoinColumnName to make the
bridge

## Add dataloader on IndexMetadata (aka indexMetadataList in the API)

## Improve field resolver performances too

## Deprecate ClientConfig

packages/twenty-server/src/engine/metadata-modules/utils/validate-field-name-availability.utils.ts

@@ -1,18 +1,18 @@
 import { compositeTypeDefinitions } from 'src/engine/metadata-modules/field-metadata/composite-types';
 import { computeCompositeColumnName } from 'src/engine/metadata-modules/field-metadata/utils/compute-column-name.util';
 import { isCompositeFieldMetadataType } from 'src/engine/metadata-modules/field-metadata/utils/is-composite-field-metadata-type.util';
-import { ObjectMetadataEntity } from 'src/engine/metadata-modules/object-metadata/object-metadata.entity';
+import { ObjectMetadataItemWithFieldMaps } from 'src/engine/metadata-modules/types/object-metadata-item-with-field-maps';
 import {
   InvalidMetadataException,
   InvalidMetadataExceptionCode,
 } from 'src/engine/metadata-modules/utils/exceptions/invalid-metadata.exception';
 
 const getReservedCompositeFieldNames = (
-  objectMetadata: ObjectMetadataEntity,
+  objectMetadata: ObjectMetadataItemWithFieldMaps,
 ) => {
   const reservedCompositeFieldsNames: string[] = [];
 
-  for (const field of objectMetadata.fields) {
+  for (const field of Object.values(objectMetadata.fieldsById)) {
     if (isCompositeFieldMetadataType(field.type)) {
       const base = field.name;
       const compositeType = compositeTypeDefinitions.get(field.type);
@@ -30,12 +30,16 @@ const getReservedCompositeFieldNames = (
 
 export const validateFieldNameAvailabilityOrThrow = (
   name: string,
-  objectMetadata: ObjectMetadataEntity,
+  objectMetadata: ObjectMetadataItemWithFieldMaps,
 ) => {
   const reservedCompositeFieldsNames =
     getReservedCompositeFieldNames(objectMetadata);
 
-  if (objectMetadata.fields.some((field) => field.name === name)) {
+  if (
+    Object.values(objectMetadata.fieldsById).some(
+      (field) => field.name === name,
+    )
+  ) {
     throw new InvalidMetadataException(
       `Name "${name}" is not available`,
       InvalidMetadataExceptionCode.NOT_AVAILABLE,