[Bug]: Cannot configure sentinel via ENVVARS

I am trying to configure Redis Insight with config as code, and have seen that you can do this via environment variables, or a JSON file.

Preconditions
None

Steps to reproduce (How to reproduce what you found step by step)
I can see envvars available at https://redis.io/docs/latest/operate/redisinsight/configuration/#preconfigure-database-connections-using-environment-variables for

• RI_REDIS_HOST
• RI_REDIS_PORT
• RI_REDIS_USERNAME
• RI_REDIS_PASSWORD

But this is no RI_REDIS_TYPE where I can configure Sentinel.

I have to go to the UI, add a database of type sentinel, and then export as JSON, and then use RI_PRE_SETUP_DATABASES_PATH. I do this by adding this into a ConfigMap, before mounting that into the container under a path.

However, if I do this, I cannot inject passwords into the JSON file under the password and sentinelMaster.password keys as they are not known at Helm templating time.

I'd like to either:

• be able to set sentinel in envvars
• or
• have the JSON file support envvars like $RI_REDIS_PASSWORD

Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)

Additional context (Operating system, version of Redis Insight, Redis database version, Redis module version, database type, connection type, logs, or any other information)

• v2.70.1
• Kubernetes vanilla deployment
• Deployed using a helm chart

Start with the Redis Insight environment-variable configuration documentation and the RI_PRE_SETUP_DATABASES_PATH handling described in the issue; no source files or tests are named. Trace how database connection types and passwords are loaded in a Kubernetes/Helm deployment, then define tests for the chosen approach. Done means Sentinel can be configured without UI-only steps or unavailable secret values.