Cron.Ng The Crongular scheduler

**Feature:**
This will create the cron.ng cron scheduler.

**Ticket:**
https://app.asana.com/0/22491639454642/22670128190663

**Review Checklist:**
- [x] All major functionality integration docs need to be bubbled up to an appropriate major module
- [x] All new classes have class level comments (just above the class itself)
- [x] All new modules with code in them have module level comments (just above the module)
- [x] All new public methods have at least the parameters documented and the return, when needed also a quick description

**Task List:**
- [x] CI Passing
- [ ] Release note created and linked in asana ticket

**Only Then:**
- [ ] Merge PR
- [ ] Move ticket in Asana
Kinda weird to use broadcast for a single event receiver. What's the grand plan for the use of broadcast.

Might be better to scope the callback onto the job itself to avoid job name collision issues. We already have access to the specific instance of the job here. We need some sort of `ActiveSupport::Callbacks` to extend the job but I think that would be better since devs would not need to worry if there are other jobs that matches the name of their new job.