6255 move services from messaging common module into the correct module and refactor them

[bosiraphael]

Closes #6255

• Move files from messaging/common into the correct module
• Remove common module between calendar and messaging calendar-messaging-participant-manager
• Update and fix massaging and calendar participant matching
• Create MatchParticipantModule

[greptile-apps]

PR Summary

This pull request refactors and relocates services from the messaging/common module to their appropriate modules, aiming to avoid circular dependencies and improve code organization.

• File Relocations: Moved is-email-blocklisted.util.ts and its test to blocklist module. Updated import paths accordingly.
• Service Deletions: Removed add-person-id-and-workspace-member-id.service.ts from calendar-messaging-participant-manager.
• Method Updates: Added workspaceId parameter in calendar-save-events.service.ts and renamed methods in calendar-event-participant.service.ts.
• Module Refactors: Updated messaging-common.module.ts to remove several services and streamlined messaging-import-manager.module.ts with new imports and providers.
• Job and Utility Adjustments: Updated method calls and import paths in various job and utility files to reflect the new module structure.

_{30 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}

[charlesBochet]

Great improvement, I've left additional comments

[charlesBochet]

I don't think you have to pass the workspaceId here, you could get it from the scopedWorkspaceContextFactory (see twenty-orm.manager.ts). This would avoid the whole drill down and secure the behavior to avoid proposing where the workspace can be provided. That's being said I'm not 100% sure about this pattern of auto-resolving the workspaceId from the request

[bosiraphael]

Done

[charlesBochet]

do we still need this one? looks like nothing is provided or exported