Setup relations for remote objects

[thomtrp]

New strategy:

• add settings field on FieldMetadata. Contains a boolean isIdField and for numbers, a precision
• if idField, the graphql scalar returned will be a GraphQL id. This will allow the app to work even for ids that are not uuid
• remove globals dateScalar and numberScalar modes. These were not used
• set limit as Integer
• check manually in query runner mutations that we send a valid id

Todo left:

• remove WorkspaceBuildSchemaOptions since this is not used anymore. Will do in another PR

[github-actions]

TODOs/FIXMEs:

• // TODO: function should work for other types than Postgres: packages/twenty-server/src/engine/metadata-modules/remote-server/remote-table/remote-table.service.ts
• // TODO: function should work for other types than Postgres: packages/twenty-server/src/engine/metadata-modules/remote-server/remote-table/remote-table.service.ts

Generated by 🚫 dangerJS against ae0f24f

[Weiko]

• Can be done in an upcoming PR but since we don't want to allow field creation for remote objects can we hide the "add field" in the settings?

[Weiko]

I couldn't make it work with integer primary keys

[Weiko]

I have typecheck errors such as inside FieldMetadataItem.ts not returning isRemote

[Weiko]

LGTM! 👏 @thomtrp