upgrade mongodb to 4.4

[longrunningprocess]

Fixes #1520

Description

There is a desire to utilize aggregation pipelines and take advantage of possible perf improvements.

Type of Change

• infrastructure upgrade

Screenshots

N/A

Checklist

• I have performed a self-review of my own code
• I have reviewed the title/description of this PR which will be used as the squashed PR commit message
• Create an issue for the upgrade to 5.0 and reference https://www.mongodb.com/docs/v5.0/release-notes/4.4-upgrade-standalone/
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works

How to test

Please describe how to test and/or verify your changes. Provide instructions so we can reproduce. Please also provide relevant test data as necessary. These instructions will be used for QA testing below.

• A general smoke test in addition to successful automated tests should be enough to move forward with this one. upgrade mongo to 4.2 is a good reference as well.

qa.languageforge.org testing

Testers: Check the box and put in a date/time to sign-off/attest the feature works as expected on qa.languageforge.org

• Tester1 (YYYY-MM-DD HH:MM)
• Tester2 (YYYY-MM-DD HH:MM)

[github-actions]

Unit Test Results

368 tests   368 ✔️  10s ⏱️
    1 suites      0 💤
    1 files        0 ❌

Results for commit c4479ad.

[megahirt]

I read the documentation on upgrading to 4.4 from 4.2 and there doesn't seem to be anything actionable, so seeing how the tests pass, this looks good to go

[megahirt]

LGTM thanks!

[longrunningprocess]

I read the documentation on upgrading to 4.4 from 4.2 and there doesn't seem to be anything actionable, so seeing how the tests pass, this looks good to go

Agreed, it seemed the same to me

[longrunningprocess]

created #1568

[megahirt]

I tested this by verifying that QA is functioning normally (utilizing the mongodb database as expected)