Fix 0.32

[charlesBochet]

• Removing unique constraint creation in 0.32 as we have a dependency on sync-metadata and sync-metadata has a dependency on it if we keep it.
• sync-metadata does not support well the deletion of activity + activityTarget, silently swallow the exception for now

[greptile-apps]

PR Summary

This PR implements changes to enforce unique constraints for person emails in version 0.32, with related adjustments to foreign key handling and entity definitions.

• Removes optional flag for person email uniqueness in /packages/twenty-server/src/database/commands/upgrade-version/0-32/0-32-enforce-unique-constraints.command.ts, making it mandatory
• Adds temporary workaround in workspace-migration-runner.service.ts to handle missing 'activityId' foreign key during 0.32 upgrade
• Shifts from decorator-based to database-level uniqueness by removing @WorkspaceIsUnique() from person.workspace-entity.ts
• Handles duplicate emails by appending incremental numbers while preserving the original email structure
• Includes migration script to safely update existing duplicate records without data loss

_{3 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: This temporary hack silently ignores missing foreign key constraints for activityId columns. Consider adding logging to track these occurrences.

[greptile-apps]

style: Consider removing the commented-out decorator entirely instead of leaving it as a comment, since the uniqueness is now handled by the migration script

[greptile-apps]

logic: Removing uniqueness constraint on emails could allow duplicate contacts to be created - ensure proper validation is implemented at the application level