Add API endpoint to migrate standalone connectors to composer-managed deployment

[romain-filigran]

Use case

OpenCTI previously supported connector deployment in "standalone" mode. Recently, we introduced the ability to manage connector deployment through our composer via the UI interface. As a result, we need to migrate existing standalone connectors to composer-managed deployments.

Current Workaround

Currently, there is no automated way to migrate standalone connectors to the new composer-managed deployment model. Manual migration is error-prone and risks losing critical connector state and configuration.

Proposed Solution

Introduce a new API endpoint in OpenCTI to facilitate the migration of standalone connectors to composer-managed deployments. This API should handle the redeployment process while preserving essential connector information.

The API must transfer and preserve the following information during redeployment:

• Connector ID: Maintain the unique identifier of the connector
• Associated User: Preserve the user account linked to the deployment
• Connector State: Retain the current ingestion state to ensure continuity of data processing

[sbocahu]

If the Associated User is not already a SA, can we migrate it to a SA ?