[Feature Request]:DB Index-wise Data Export/Import in Redis Insight

Problem description (Describe the problem you would like to solve with this feature request or suggested idea).
Currently, Redis Insight lacks a direct feature to export data when migrating from one Redis server to another, especially while preserving the same data structure and DB index mappings. This creates challenges during infrastructure changes or server upgrades. There’s no built-in export/import mechanism in Redis Insight to help us selectively export keys (e.g., per DB index) or migrate the entire dataset efficiently. As a result, we are forced to use external tools or scripts, which are often error-prone and time-consuming.

How often do you encounter this problem (Describe how frequently this problem occurs).
This issue arises frequently during Redis server migrations, upgrades, backups, or when scaling infrastructure across environments (e.g., staging to production). It's particularly painful in large or multi-tenant systems where Redis databases are segregated by index.

Alternatives considered (Describe any alternative features or products you've considered).

• Using redis-cli with manual scripting to dump and restore data per DB index.
• Leveraging RDB or AOF file-level backups, which lack fine-grained control and flexibility.
• Using third-party tools that are not always compatible with Redis Insight and often have limited UI support.
  However, none of these alternatives provide the ease, control, or native integration that a Redis Insight feature would offer.

Additional information (Add any other context or details here).
An ideal feature would:

• Allow export/import of keys per DB index directly from Redis Insight.
• Support bulk export and import with filters (e.g., key patterns, TTL, etc.).
• Provide a UI option to preview data before exporting.
• Optionally support multiple formats (e.g., JSON, RDB-compatible, plain text).
  This functionality would greatly enhance usability, especially for DevOps and developers managing Redis data lifecycle across environments.

No files, tests, or entry points are identified. Start by locating Redis Insight’s existing key-management UI and Redis database-selection flows, then narrow the export/import scope around DB indexes, filters, TTL, preview, and formats. Done should mean an agreed, testable migration workflow rather than an open-ended set of options.