Migrate: Adopt Official MongoDB Image, Implement Safety Gates & Update Docs

[gabrielpetry]

Feature: Migrate to Official MongoDB Docker Image

This PR updates the MongoDB service to use the official Docker image (mongodb/mongodb-community-server) instead of the deprecated Bitnami image.

This is a critical change for better long-term maintenance, stability, and to ensure we are running on fully supported MongoDB releases.

---

Technical Changes & Migration Safety

To guarantee a clean and safe transition for all users, the following safeguards have been implemented:

1. New Volume Name to Prevent Corruption

• Change: The persistent volume for MongoDB has been renamed from mongodb-data to official-mongodb-data.
• Impact: This forces a clean install, preventing potential data corruption or runtime errors that could occur by attempting to reuse data created by the legacy Bitnami image.

2. Acknowledge Gate for Data Loss Prevention

• Change: A pre-flight check/warning is now required during the setup process.
• Impact: Users must explicitly acknowledge this migration and confirm that old data in the mongodb-data volume will be ignored and lost. This step ensures users migrating from an older deployment are aware of the data path and prevents accidental loss.

3. Resolution of Startup Error

This PR directly addresses the common RuntimeError that occurs when users attempt to start the new official image without first acknowledging the migration or dealing with the legacy volume. The pre-flight check ensures users are routed to the proper migration steps rather than hitting a generic error:

[MatthiasKuehneEllerhold]

Nitpicking: In the compose.database.yml youve used oficial_mongodb_data instead of official_mongodb_data.