[connectors] fix: Use csv document internalId for tableId, add csv in migration

[tdraier]

Description

Currently, for csv files in google/microsoft, we use the google/ms id as a table_id . We should rather use here our internalId to avoid conflicts.
Added google/microsoft csv in parents migration .

We have only one datasource with csv enabled (doctolib), we may need a full reindex as the table ids are changed for csv.

Risk

Deploy Plan

Deploy connectors
Reindex datasources with csv

[JulesBelveze]

Not sure to understand why we to retrieve both worksheet and ms-excel in microsoftTables while only retrieving text/csv in GDrive and not include application/vnd.google-apps.spreadsheet?

[tdraier]

Not sure to understand why we to retrieve both worksheet and ms-excel in microsoftTables while only retrieving text/csv in GDrive and not include application/vnd.google-apps.spreadsheet?

For microsoft, we have :

• worksheets
• csv file which are application/vnd.ms-excel ( I may also catch text/csv )
  All of these are in the same table microsoft_nodes

For google :

• sheets
• csv file (text/csv)
  File which are application/vnd.google-apps.spreadsheet are actually parsed as google sheets (equivalent to application/vnd.openxmlformats-officedocument.spreadsheetml.sheet for microsoft)
  Here sheets are in a different table than files.

[JulesBelveze]

@tdraier Gotcha 👌🏼