Scheduler needs to maintain its base fields properly

I could not get patch #11 to apply without errors so I created a new patch. I also added a post update hook to address the issue mentioned in comment #24.

Removing the code that uses the lightning_scheduler.migrator service from the previous patch.

Updated patch to fix tests.

Updating patch to fix coding standards.

@minirobot,
if you're actually using this project I highly suggest having a look at my comment #73 here:
#3003907-73: Performance - load since last cron rather than since January 1, 1970 →

with that said, please try out scheduled transitions. Scheduled transitions works with one or many translations of an entity.
However if you want to continue using lightning_scheduler I highly suggest writing a patch based on my comment #73. Without this fix your clients site will become incredibly slow over time slower and slower unless you resolve this code issue. I'd say it's a critical bug because if nothing is done the entire site will become unusable over time and will greatly tax your servers resources unless this issue is fixed.

Hi!

The patch at #33 didn't work for me because my installation 4.0.0 is a submodule of lightning_workflow and has slightly different code. I rerolled it for 4.0.0 as a submodule.

@neptune-dc , save yourself a lot of trouble, switch to the scheduled_transitions module instead
lightning_scheduler has some serious performance bugs , your site performance will gradually get worse over time if you keep this module installed, it reprocesses all previously processed revisions going back to the EPOC time, January 1st 1970, if you can imagine what this does to performance, think twice about using this module. Scheduled Transitions actually works! and doesn't have performance and scalability bugs. Scheduled Transitions actually works with translations also