fix(node-core): passthrough node-cron context

[sebws]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

- [ ] If you've added code that should be tested, please add tests.

• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

node-cron passes context to the functions which this integration does not.

the types here seem to be largely irrelevant as consumers just get the actual node-cron type. however, it might be better to install node-cron as a devdependency and then import and use types from it to get consistency

[chargome]

Makes sense to me, should we add a dev dep for this @andreiborza ?

[andreiborza]

Yea, we can add that in this PR.

[sebws]

tbh it might be a bit harder, given this wrapper already wraps incorrectly and doesn't support node-cron fully, e.g. string referring to a file instead of a callback.

however, just for fun, perhaps it would be more accurate to do

"peerDependencies": { 
  "node-cron": "^4"
},
"peerDependenciesMeta": {
  "node-cron": {
    "optional": true
  }
}

[sebws]

maybe a different style of wrapper would be more accurate that passed through without manipulation and would add event listeners, leaving node-cron to fully handle the execution.

although I'm not sure if that would work with how withMonitor works