🧩 Enhanced Controlled Export/Import Process with Intelligent Conflict Management

📄 Description

This PR introduces a new controlled Export/Import process for Flowise workspaces, allowing users to precisely manage which elements to import, duplicate, or update.
The goal is to provide greater control and transparency while maintaining data isolation and credential security across workspaces.

This functionality is currently tested and running correctly across all exportable elements.

✅ Key Features

1. Granular Import Control

• Users can decide per item whether to:
  • Update the existing element (replace content)
  • Duplicate it (create a new UUID with a name suffix, e.g., -duplicate)
  • Skip import altogether
• Conflict checking is now based on item names, not UUIDs, ensuring workspace isolation and independence.

2. Supported Elements

The controlled import process is validated for the following exportable elements:

AgentFlow, AgentFlowV2, AssistantFlow, AssistantCustom,
AssistantOpenAI, AssistantAzure, ChatFlow, CustomTemplate,
DocumentStore, Tool, Variable

For the following, items always appear as "New Items" on the second tab (user decides whether to import them):

Executions, ChatMessages, ChatMessageFeedbacks, DocumentStoreFileChunks

🔐 Credential Handling & Security

• Exported data does not include secret credential values — only credential NamesIds are included.
• During import:
  • If credentials exist on the target instance, they are automatically reconnected.
  • If credentials are missing, fields remain empty (safe default).
• This ensures:
  • No exposure of sensitive data (UUIDs or secret values)
  • Automatic reconnection for smooth post-import operation

🧠 Implementation Details

• Conflict management uses element names as keys for comparison.
• The system displays conflicts in a dedicated "Conflict Tab", where users can:
  • Choose to update, duplicate, or skip each conflicting element.
• No automatic imports — user confirmation is required for every item.
• The export process now includes credential name mapping without exposing secrets.
• Fully compatible and tested within a single workspace setup.

⚠️ Security Considerations

Enterprise Context

• Importing data into another workspace creates new UUIDs, ensuring full isolation.
• The original workspace data cannot be modified from another workspace.

SaaS Context

• Since matching is name-based, not UUID-based, data conflicts cannot expose other users’ data.
• The Conflict Tab guarantees user approval before overwriting or duplicating data.

🧭 Next Steps

• Validate under multi-workspace environments
• Add optional "Sanitize Sensitive Info" toggle for enterprise/SaaS export contexts
• Finalize UX refinements for the conflict resolution interface