TimeProvider isn't used everywhere

[nulltoken]

Describe the bug
There are at least three places where TimeProvider isn't used and where DateTimeOffset is preferred

• ExecutionProgress
• JobState
• JobWorker

Should we align everything to TimeProvider?

[linkdotnet]

You mean in our public API? For example triggering instant jobs?

[linkdotnet]

If so - I don't think TimeProvider would add value here. There is already an interface if mocking / stubbing is the issue. So I am not sure what the user would gain

[nulltoken]

Lots of places relies on the TimeProvider, which is handy from the testing standpoint.

However, following places don't.

[nulltoken]

Those DatetimeOffset.Now won't play nice with FakeTimer.Advance()

[linkdotnet]

Okay that is fair! I assume it should be fairly straightforward to pass in a TimeProvider via the ctor.