fix: revert changes to match 1.6.3, apart of resume on restart

[b0dea]

@code-xhyun this is my last try to get 'nextRunAtset onnull` fixed.

As a note, on 1.6.3 - it works, nextRunAt gets set up correctly.

So 100% some of my changes are buggy.
With this change, I see no other differences between this and 1.6.3 - apart of the resumeOnRestart method which should not affect anything else.

So

• please take a look and see if we should change anything else. Ideally run it yourself also, maybe it's something wrong on my side.
• if you have no time - I am going to forward my apologize for the mistake(s) and I ask you to please revert all back to 1.6.3 which will keep all the original issues, but at least nextRunAt works as expected (tested myself). Like this we avoid making people use the buggy version.

I am sorry for this. Thank you.

[code-xhyun]

🎉 This PR is included in version 1.6.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[code-xhyun]

Thx bro :) @b0dea

[b0dea]

Thx bro :) @b0dea

@code-xhyun I can confirm now that the issue is no longer present. I will work these days on improving the bit even more the resumeOnRestart and will look more into the default date so we avoid re-running randomly the non-recurrent jobs. Thanks