[Feature Request]: Support Docker Swarm secrets (/run/secrets)

Problem description (Describe the problem you would like to solve with this feature request or suggested idea).

Provide support for Docker Swarm secrets mounted at /run/secrets so that sensitive values (for example RI_ENCRYPTION_KEY) can be supplied to RedisInsight containers securely. Today these values must be passed via environment variables or mounted files manually; built-in support to read /run/secrets/<NAME> would simplify secure deployments with Docker Swarm stacks and reduce the risk of accidentally exposing secrets.

How often do you encounter this problem (Describe how frequently this problem occurs).

This issue occurs whenever RedisInsight is deployed to Docker Swarm (or other orchestrators that expose container secrets as files under /run/secrets). It affects users who prefer secrets management over plaintext environment variables for production deployments.

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

• Continue using environment variables (less secure in some deployment scenarios).
• Mount secret files into the container manually and configure RedisInsight to read from a custom path (works but is manual and error-prone).
• Use external secret management solutions and inject values at runtime (adds operational complexity).

Additional information (Add any other context or details here).

• Example expected behavior: if /run/secrets/RI_ENCRYPTION_KEY exists and is readable, RedisInsight uses its contents as the encryption key. If not present, fall back to the existing environment variable RI_ENCRYPTION_KEY if set.
• This change should be backward-compatible and optional; existing env-var-based workflows must continue to work.
• Path example: /run/secrets/RI_ENCRYPTION_KEY.

Start by locating the existing RI_ENCRYPTION_KEY environment-variable handling and the Docker deployment configuration. Check how a readable /run/secrets/RI_ENCRYPTION_KEY should interact with the existing environment-variable fallback. Done means Docker Swarm secret values work without breaking existing environment-variable workflows, with coverage for both paths.