feat(db): add MongoDB integration tests & CI support

[sidshas03]

• Add comprehensive MongoDB integration tests (not mocked)
• Add database comparison tests for file vs MongoDB parity
• Add CI integration with MongoDB service
• Add local Docker-based testing support
• Add test scripts: test:mongo and test:mongo:docker
• Improve MongoDB client error handling

pr-1168(#1168)

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	0ff5641
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/68c898ebf169a70008a29d4c

[sidshas03]

Thank you for checking, @coopernetes sir. This is not a duplicate of PR #1165.

While #1165 focuses on Cypress E2E test setup and Docker Compose adjustments, this pull request introduces MongoDB integration test coverage, including:

• MongoDB-backed test cases for core operations
• docker-compose.mongo.yml for local and CI support
• New test scripts (test:mongo, test:mongo:docker)
• MongoDB client error handling improvements

These changes are related to issue #1168 and are separate from the Cypress work in #1165.

Please let me know if anything needs to be adjusted or split further. I am happy to revise based on feedback.

[kriswest]

Conflicts to resolve and all 34 mongo tests are failing due to a lack of a conneciton string

[kriswest]

@sidshas03 could you take a look at the conflict and test failures (Error: MongoDB connection string is not provided) and we'll see about getting you a review. @coopernetes tells me that this is orthogonal to his PR and hence quite valid so many thanks for the contribution.

[sidshas03]

Hey @kriswest, im really sorry i was unwell for weeks. thanks for the nudge and for checking with @coopernetes.

Ack on both points:

• I see the merge conflicts with main; I’ll rebase and fix those.
• The Mongo tests are red because there’s no connection string in CI.

[coopernetes]

@sidshas03 given how we are in the middle of a very significant refactoring of our test framework (moving from chai to Vitest) via #1202, we should wait for that PR to land in main so you can take advantage of a more modern test setup. Then we can integrate these new integration tests.