Replace mongodb-runner with mongodb-memory-server

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently, we are using mongodb-runner to spin up MongoDB test DBs in CI.

There have been recent incidents, where the latest MongoDB version was not available via mongo-runner.

Feature / Enhancement Description

Switch to mongodb-memory-server.

Example Use Case

n/a

Alternatives / Workarounds

Keep excluding recent MongoDB versions from testing in the CI.

3rd Party References

n/a

[Moumouls]

i guess i can help on this one @mtrezza i noticed recently some issue during testing on parse where mongo runner don't close correctly the server, and we need to go to task manager to close the mongo runner

[mtrezza]

Same annoying experience. But are there any cons?

For example:

When you terminate your script or call stop(), the MongoDB server(s) will be automatically shutdown.

That means when an error occurs during debugging and the script terminates, the MongoDB data is lost and cannot be inspected. This could make it more difficult to debug, because it's all in memory. But I guess if we keep the current scripts in package.json, then the MongoDB server could run on a separate process like npm run test:mongodb:runnerstart? I guess we's have to simplify try it out.