refactor: minor changes to remove mongo deprecation warnings

[Moumouls]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Close #7623, #7624

Related issue: #7623, #7624

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

[codecov]

Codecov Report

Merging #7626 (8770cb4) into master (936b5ec) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #7626      +/-   ##
==========================================
+ Coverage   93.97%   94.00%   +0.02%     
==========================================
  Files         181      181              
  Lines       13354    13354              
==========================================
+ Hits        12549    12553       +4     
+ Misses        805      801       -4     

Impacted Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	93.33% <100.00%> (+0.86%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 936b5ec...8770cb4. Read the comment docs.

[Moumouls]

with this fix no more warnings noticed on test project. this pr is good to go !

[mtrezza]

Not a fix, since the issue is not a bug, see contribution guide for how to use commit types.

Can you please

• adapt the change log entry
• delete the todos that don't apply to this PR

[Moumouls]

done @mtrezza

[mtrezza]

Looks good! Removed unrelated changes.

[parseplatformorg]

🎉 This change has been released in version 5.0.0-alpha.2

[parseplatformorg]

🎉 This change has been released in version 5.0.0-beta.1

[rocxteady]

You said it was a bug here: #7345 (comment)
But you said it is not a bug here in this pull request.

[mtrezza]

It's not a bug as it doesn't require a new release. We have no "refactor" label in GitHub issues, so it was classified as trivial bug, but it's not merged a bug but as a refactor, which indeed can cause confusion. Maybe we should add a refactor label for issues.

[parseplatformorg]

🎉 This change has been released in version 5.0.0