RJS-2854: Adding a ThreadSafeFunction-based scheduler for Core on Node.js

[kraenhansen]

What, How & Why?

This closes #6772 by implementing a utils::Scheduler based on the Napi::ThreadSafeFunction primitive.

Note: In order for the uncaught exceptions thrown by the Node.js addon, the node process must be started with a --force-node-api-uncaught-exceptions-policy flag enabled. This was added under a flag to "not breaking existing running Node-API add-ons.".

https://github.com/nodejs/node/blob/cd39578e53d6502de03f15620d15835b86954ac8/src/node_api.cc#L85-L115

Alternatively the following warning will be logged:

(node:17922) [DEP0168] DeprecationWarning: Uncaught N-API callback exception detected, please run node with option --force-node-api-uncaught-exceptions-policy=true to handle those exceptions properly.

☑️ ToDos

• Rebase when Refactored Node test environments to share more #6798 merge.
• Rebase when Passing scheduler to EventLoopDispatcher, schedulerWrapBlockingFunction and through RealmConfig realm-core#7903 merge and gets released.
• Fix outstanding tests that are currently timing out.
• Investigate passing the enforceUncaughtExceptionPolicy template parameter to avoid the warning when throwing uncaught exceptions.
• 📝 Changelog entry
• 📝 Compatibility label is updated or copied from previous entry
• 📝 Update COMPATIBILITY.md
• 🚦 Tests
• 📦 Updated internal package version in consuming package.jsons (if updating internal packages)
• 📱 Check the React Native/other sample apps work if necessary
• 💥 Breaking label has been applied or is not necessary
• 🔔 Mention @realm/devdocs if documentation changes are needed

[kraenhansen]

I thought my implementation was done, but it turns out tests were still failing 🤔 This is likely never going to get merged.