[Zendesk] Add the brandId in the internal IDs for tickets and articles

[aubin-tchoi]

• An assumption was made in the code that the ticketIds and articleIds were unique within a connector.
• This turns out to not be the case as multiple brands will have clashing IDs.
• As a result, the internal ID of an article or a ticket has to contain the brandId.

Proposed course of actions:
- Start inserting document_id x2 (with and without the brandId) in connectors.
- Force resync all the Zendesk connectors.
- Update connectors to use the new IDs in contentNode (fixes https://github.com/dust-tt/tasks/issues/1870).
- Update connectors to only upsert the new IDs.
- Delete all documents using old IDs.

Updated course of actions:

• Start inserting the new document_id (with the brandId) and deletes the documents using the old ones (without the brandId) in connectors.
• Force resync all the Zendesk connectors.
• Update connectors to use the new IDs in contentNode.
• Fix the db fetch to use the brandId + ticketId/articleId/categoryId (fixes https://github.com/dust-tt/tasks/issues/1870).
• Delete all documents using old IDs if any remaining.

Note: no migration required on front, the documents affected are never parents.

[aubin-tchoi]

@spolu LGTY?

[spolu]

@aubin-tchoi LGTM

[aubin-tchoi]

note: no single ticket or article in data_source_views

SELECT dsv.* 
FROM data_source_views dsv
JOIN data_sources ds ON ds.id = dsv."dataSourceId"
WHERE ds."connectorProvider" = 'zendesk';

same goes for agent_data_source_configurations

SELECT dsv.* 
FROM agent_data_source_configurations dsv
JOIN data_sources ds ON ds.id = dsv."dataSourceId"
WHERE ds."connectorProvider" = 'zendesk';

[spolu]

Good to know 👍

[aubin-tchoi]

Closing this as it was handled in #9723 and a check on the db select document_id from data_sources_documents where document_id similar to 'zendesk-ticket-\d+'; shows that all tickets have been migrated