feat: workspace health target column map fix

[magrinj]

This PR is implementing the target-column-map kind in the --fix option of workspace:health command.
The core was created here #3863

Fix #3844

[charlesBochet]

@magrinj I think the refactoring makes sense.

I've tested and these are my feedbacks:

• default-value doesn't seem to work anymore. I've removed the defaultValue on a text field and it was not detected
• regarding targetColumnMap, the following cases are not handled:

1. wrong columnName { "value": "_columnId" } instead of { "value": "columnId" } + rename the column if the column is badly named
2. wrong columnName { "value": "sdlkjfls" } instead of { "value": "columnId" } + rename the column in postgres schema if the column is badly named
3. targetColumnMap of RELATION should be {}
4. targetColumnMap is {"toto": "companyId"}

Is there a way to easily compute the right targetColumnMap from fieldMetadata. If it's too complex, maybe we should not invest too much here as we are going to deprecated targetColumnMap.
In this case, just fix default-value and we can merge. If you see an "easy" way of computing it and fixing it, let's go with that.

Also, fixing targetColumnMap might actually create more "MISSING_COLUMN" cases, as we don't migrate columns but I think it's fine, we can manually fix those, they should be pretty rare actually

[github-actions]

TODOs/FIXMEs:

• // TODO: run in a dedicated job + run queries in a transaction.: packages/twenty-server/src/workspace/workspace-sync-metadata/commands/sync-workspace-metadata.command.ts

Generated by 🚫 dangerJS against 0aeb022

[charlesBochet]

Tested, it works well!