fix(react): resolve mongodb image pull error by upgrading to working tag

[DivyanshuVortex]

Summary of Changes

This PR resolves the docker compose startup failure caused by Broadcom/Bitnami's deletion of versioned community tags (e.g., bitnami/mongodb:4.4) from their public Docker Hub registry in late 2025.

It upgrades the database layer in packages/react/docker-compose.yml to a working and pullable image setup.

Fixes : #1292

How to Verify / Test

1. Navigate to the react package directory:

cd packages/react

2. Purge old local volume configurations:

docker compose down -v

3. Launch the stack:

docker compose up -d

4. Verify both containers are running successfully:

docker compose ps

PR Test Details

Note: The PR will be ready for live testing at https://rocketchat.github.io/EmbeddedChat/pulls/<pr_number> after approval. Contributors are requested to replace <pr_number> with the actual PR number.

[CLAassistant]

All committers have signed the CLA.

[DivyanshuVortex]

Question for Maintainers: Which approach do you prefer?

I have implemented Approach 1 (the cleanest change keeping the exact same image namespace), but I can instantly pivot this PR to Approach 2 depending on your preferred architectural style:

🔹 Approach 1: Use bitnami/mongodb:latest (Currently Implemented in this PR)

• Pros: Keeps the docker-compose.yml file completely clean and keeps the exact same image name.
• Cons: Using :latest is non-deterministic (future pulls will always download whatever new version Bitnami releases).

🔹 Approach 2: Migrate to mongodb/mongodb-community-server:8.0-ubi8

• Pros: The most robust, production-grade option. Officially supported by MongoDB & Rocket.Chat.
• Cons: Requires adding a custom inline entrypoint bash script to automatically initiate the replica set (rs0), making the docker-compose.yml file look more verbose.

Please let me know which approach you prefer to merge, and I will gladly update this branch to match!

---