Scheduled task infrastructure

[Piedone]

As discussed starting from this coment: #3991 (comment) Once this is done it can be used by the Publish Later module and perhaps later by an Archive Later module (#5754).

[Piedone]

@deanmarcussen I believe you're working on this one, right? If yes, could you please assign?

[hishamco]

Dean's started working on schedule infrastracture APIs which ArchiveLater & PublishLater sit on top of it. I already did some progress in this for scheduling a content only, after a sudden I saw a comment from dean that he is already in the middle of the work, so I stopped to avoid duplicate and save time for us

[hishamco]

@Piedone we could merge the associated PR and then rebase on Dean's work or wait until he submit his PR

[Piedone]

I'd wait for Dean's work. That would prevent introducing new technical debt, and also serve as a test of the API being used by another developer.

[Piedone]

@deanmarcussen previously you said you're working on this but I can't find any related PR. Could you shed some light on this, please?

This is perhaps related for #10935 though we could merge that and revise once this is done.

[hishamco]

At least we can keep working on it if it's still WIP

[Piedone]

@deanmarcussen could you reply here, please?

[Piedone]

Related: #760

[Piedone]

See Dean's POC for using Quartz.NET here: #760 (comment).

[Piedone]

Related: #4092