[REQUIRES_CACHE_FLUSH_FOR_FIELD_AND_OBJECT]FlatFieldMetadata and FlatObjectMetadata required universal (#17557)

# Introduction
In this PR we're migrating both the `field` and `object` metadata to be
using the new `FlatEntityFromV2` that requires all the
`UniversalFlatEntityExtraProperties` to be spread at the flat entity
root.

This means that we have to update all of their flat declaration

This type swap allows to isole a specific entity migration into his own
type scope and avoid to have everything handled at once

```ts
/**
 * Currently under migration but aims to replace FlatEntity afterwards
 */
export type FlatEntityFromV2<
  TEntity,
  TMetadataName extends AllMetadataName | undefined = undefined,
  TInnerFlatEntity extends { __universal?: unknown } = FlatEntityFrom<
    TEntity,
    TMetadataName
  >,
> = Omit<TInnerFlatEntity, '__universal'> & TInnerFlatEntity['__universal'];

```

## Impact
Both object and field:
- Create input transpilation utils
- from entity to flat tools
- mocks

## Note
Removed from the universal extra properties the jsonb properties that do
not contain a serialized

## Next
Next step is to incrementally make the builder and runner expect
`UniversalFlatEntity` for both of these metadata
This way we will be able to fully migrate an entity e2e typesafely

packages/twenty-server/src/engine/metadata-modules/logic-function/utils/from-logic-function-entity-to-flat-logic-function.util.ts

@@ -37,12 +37,6 @@ export const fromLogicFunctionEntityToFlatLogicFunction = ({
     __universal: {
       universalIdentifier: logicFunctionEntity.universalIdentifier,
       applicationUniversalIdentifier,
-      publishedVersions: logicFunctionEntity.publishedVersions,
-      toolInputSchema: logicFunctionEntity.toolInputSchema,
-      cronTriggerSettings: logicFunctionEntity.cronTriggerSettings,
-      databaseEventTriggerSettings:
-        logicFunctionEntity.databaseEventTriggerSettings,
-      httpRouteTriggerSettings: logicFunctionEntity.httpRouteTriggerSettings,
     },
   };
 };