Upgrade MongoDB dev image to v8 #286

[joelvdavies]

Description

See title. I didnt observe any impact even when using the old data from 7.0, but to be safe you can delete the mongodb/data folder before starting anything.

If you really want to keep the data, you will need to follow the instructions found here https://www.mongodb.com/docs/manual/release-notes/8.0-upgrade-standalone/, or otherwise dump the data, delete the directory, start the upgraded version, restore the data from the dump.

No frontend CI change needed, it pulls this repo and starts from the docker compose file.

Other notes

• I removed the .keep files from the mongodb & minio folders. I realised we dont do that in ims-api, and permissions were fine when I deleted them and let docker create them from the mounts.

Testing instructions

Add a set up instructions describing how the reviewer should test the code

• Review code
• Check Actions build
• Review changes to test coverage

Agile board tracking

Closes #286

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.51%. Comparing base (ec42431) to head (616ec1b).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #287   +/-   ##
========================================
  Coverage    83.51%   83.51%           
========================================
  Files           25       25           
  Lines          728      728           
========================================
  Hits           608      608           
  Misses         120      120           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.