Feat(contact-tagging): Add support tagable contacts with bulk action

[JumpLink]

Contact Tagging System Implementation

Description

This PR implements a comprehensive contact tagging system by aligning it with the existing Callout Responses tag functionality. The changes include:

• Removal of legacy tag implementation from ContactProfile
• New tag system aligned with Callout Responses tags
• New ContactTagController for managing contact tags
• Batch update capabilities for contacts
• Enhanced filtering with pagination support
• Database migrations for tag storage

Key Changes

• Added ContactTagController with CRUD operations for global tags
• Implemented batch update functionality for multiple contacts
• Created new DTOs and transformers for tag management
• Updated filtering system to support tag-based queries
• Added database migrations for tag storage
• Aligned tag management UI components

Testing Checklist

Tag Management

• Create, edit and delete tags
• Assign tags to individual contacts
• Batch assign tags to multiple contacts
• Remove tags from contacts
• Test tag search functionality

Filtering & Pagination

• Test tag-based filtering with pagination
• Verify combined filters (tags + other filters)
• Test filter persistence across pages
• Verify performance with large datasets

Integration Tests

• Verify Callout Response tag filtering still works
• Test tag migration from old system
• Verify API responses for tag operations
• Test error handling for invalid operations

UI Components

• Test TagEditorForm functionality
• Verify ToggleTagButton behavior
• Test tag selection in filters
• Verify tag display in contact lists

Related Components

• ContactTagController
• TagTransformer
• Contact filtering system
• Tag migration scripts
• Tag management UI

Translations Checklist

• Updated translations in Google Sheet
• Merge new translations in Google Sheet to main sheet

[JumpLink]

@wpf500 I initially based my implementation on CalloutTag , but then deviated from it. In the ContactTag model, I now only store the tags and no reference to the contact (CalloutTag stores the calloutId). Instead, I have created a contact_tag_assignments table using @ManyToMany("ContactTag", "contact") and @JoinTable({...}), which is used for the assignments. For callout responses, tags are managed per callout; for contacts, they are managed globally. Maybe you would like to take a look at my unfinished implementation? Feel free to give me suggestions on what else could be combined.

[wpf500]

A few small comments but in general this is really great 🎉. Well on it's way to being one of those magical PRs that adds a feature with a negative line count 😄

[JumpLink]

This is looking amazing so far. Thanks for adding so much documentation, cleaning up the code, giving it a better structure... on top of implementing the tagging in such a way that we could easily add more taggable entities in the future.

I was very happy to do so, I found it difficult to understand (and I still haven't fully understood it) but the tidying up and documenting helped me to do so, so it wasn't entirely self-serving ;)

[wpf500]

A few minor comments, but generally looks really great 🎉

[wpf500]

One other question: have you tested the migration against an instance that had old style tags to migrate? Did it work on dev for example?

[JumpLink]

One other question: have you tested the migration against an instance that had old style tags to migrate? Did it work on dev for example?

Yes you can look at this on dev, the old tags have been successfully preserved

[JumpLink]

With my lastest changes I have implemented:

• Ordered tags
• Wrap/break tags for items with many tags
• Improved delete tag translation
• Better error message on duplicate tag names
• Readd callout filter group for contacts
• Do not disable the toggle button if no item is selected to be able to reach the tag manager without a selection
• Keep the selection to be able to toggle multiple tags for the same selected items
• Fixed Tag Manager route from detail pages
• Make tags clickable