RI-5362 Fix nightly tests running

[pawelangelow]

TL;DR

• Switch to the redisinsight image instead of riv2, as this is the one built in the pipeline-build-docker.yml.
• Mount the /data directory to containers since it’s where redisinsight stores all the required files.
• Update the backend URL to disable SSL support: Again, the goal is to get everything running first, and then address this.

Few notes

• Tests are currently failing because they need updates. For example, in this run, the test suite with passing tests generates all required files, which is why it succeeds. The failing tests don’t produce a test-run-coverage.json file, leading to their failure. Latest run here: https://github.com/RedisInsight/RedisInsight/actions/runs/12653756107. Again - due to test not passing, the test-run-coverage file can not be generated, hence flow is failing.
• This PR focuses solely on resolving issues that prevent the tests from running properly. Updates to the test scenarios themselves will be addressed in subsequent PRs.
• There are two definitions for the RedisInsight container—one in .circleci and one in .github. Do we need the one in .circleci? Do we need the entire .circleci directory?

---

• TODO: Add some high level documentation
• TODO: Add some debug suggestions for the future

---

Nah... I want to read novels

This setup requires three components: the RedisInsight application, a Redis instance, and the test runner. Here's the breakdown:

1. RedisInsight Application
   The redisinsight Docker image bundles the RedisInsight application. To enable other containers to access necessary files, we mount a shared directory (/data). This directory stores the local database file redisinsight.db. The image definition file is located at RedisInsight/.github/build/build.Dockerfile.

2. Redis Instance
   We use containers to test against different Redis distributions and configurations, such as oss-st-6 and oss-st-6-tls. The definition files for these configurations can be found in RedisInsight/redisinsight/api/test/test-runs.

3. Test Runner
   The test runner is a separate Docker image defined by RedisInsight/redisinsight/api/test/test-runs/test.Dockerfile. This image orchestrates the tests and ensures they run against the configured Redis instances and the application.

The issues described above are currently preventing the tests from running successfully. Resolving these will allow us to proceed with further updates to the test scenarios.

[ArtemHoruzhenko]

We can't do this. Production docker image shouldn't run under root user

[pawelangelow]

@ArtemHoruzhenko fixed this. Although this is not the Dockerfile we use for production, I agree it's a good practice to run it with different user. Additionally, I think it will be nice to reuse the production Dockerfile for these tests as well, but this would be for different PR.

And a question to you - do we use circleci Dockerfile somewhere?