feat: Remove optional MongoDB service from production compose file

[dev-bre]

This pull request restructures how the MongoDB service is managed in the production Docker Compose setup. The configuration for MongoDB has been moved from the main docker-compose.prod.yml file into a new, dedicated docker-compse.mongo.prod.yml file. This change improves modularity and allows for more flexible deployment scenarios, such as using an external MongoDB service or including/excluding the local MongoDB container as needed.

Docker Compose configuration restructuring:

• Removed the mongo service and its associated mongo_data volume from docker-compose.prod.yml, making the main production Compose file cleaner and more focused on the core application and proxy services. [1] [2]
• Introduced a new docker-compse.mongo.prod.yml file that defines the mongo service, its configuration, healthcheck, and required volumes and networks, along with the app and caddy services for a complete stack.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Related Issue

Closes #(issue number)

How Has This Been Tested?

Describe the tests you ran and how to reproduce them.

Screenshots (if applicable)

Add screenshots to help explain your changes.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes