build: Upgrading dependencies for compatibility with Node 20 and general maintenance

[msohaill]

List of changes:

• Upgrading all dependencies to latest stable/compatible versions.
• No major API adjustments required apart from mongoose MongoId being instantiated with new and mongoose no longer accepting callbacks. We used to use these queryCallbackFactory and updateCallbackFactory functions that actually ran every single query twice! I've migrated and fixed this behaviour so (technically) all queries should be twice as fast now 😂
• Winston logger also needed some API updates, but nothing severe.
• Database service no longer needs to emit db connected event as Mocha has updated their runners and Mongoose buffers queries.
• Tests are fixed according to Fix unit tests #925

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

• npm run test is successful!
• Ran through most major workflows using the dashboard and all are successful/exhibit the same behaviour as prior.

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Questions for code reviewers?

None come to mind.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Listed change(s) in the Changelog
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules

[pierreTklein]

Drive-by comment: thanks for cleaning up this repository. Do you still need a review on this? Happy to review it.

[msohaill]

@pierreTklein For sure, that would be great! I think this just slipped through the cracks after the hackathon

[pierreTklein]

What's "new: true" here?

[msohaill]

By default, the newer Mongoose version returns the entity as it was before applying the update. Old Mongoose version had the opposite behaviour, so to replicate we must pass { new: true } (docs).

[pierreTklein]

Why are we parsing a stringified hacker? Could we instead just do hacker? Not a rhetorical question. I am genuinely curious.

[msohaill]

So true, I think this was the most elegant solution I could find at that point (since hacker is a complex object of complex types like ObjectId and unfortunate fields like _id so it can't be directly compared to the response data). I hadn't realized the toJSON method of the Schemas were overridden which is why the method didn't work for me. Just pushed a fix