Long running durable timers

[bachuv]

These changes allow durable timers to run longer than 7 days and resolves #14 .

Durable timer messages use queue messages which don't last longer than 7 days. To get around this, if a timer is scheduled for longer than 7 days, then the timer will go off every 3 days until the difference between the current time and the scheduled time is less than 3 days.

[bachuv]

The tests, AzureStorage_TimerLimitExceeded_ThrowsException() and ThrowExceptionOnLongTimer(), fail now because of the changes that make durable timers last longer than 7 days. Would it be best to remove them and see if they can be replaced with a test that has a shorter interval time and max time?

[cgillum]

This is looking great. Can we add a test or two to validate the behavior?

[MaximRouiller]

This is exactly what I needed. I have things to schedule that may be every 7 days, 14 days, 4 weeks, or 6 weeks.

I'd love for this to be merged yesterday 😛

[jedjohan]

Oh yes, was just implementing a complicated (to me) while loop to crank more than 7 days out of durable timers. This makes me really happy. Will there be a new maximum delay implemented ? Keep up the good work, thanks !

[bachuv]

Glad to hear that @jedjohan! No, there isn't a new maximum delay. If a timer is scheduled for longer than the maximum delay, then a new timer is scheduled every three days until the difference is less than three days. This ensures that users won't have to worry about staying within a maximum time.

[ConnorMcMahon]

A few pieces to cleanup, but the PR is shaping up nicely!

[ConnorMcMahon]

LGTM!

[cgillum]

Just a few non-blocking suggestions, but I think this is ready to be merged when you feel ready!

[MaximRouiller]

Can't wait for this to be merged. 🤩

[ConnorMcMahon]

LGTM, just look into that last comment I made.