Be consistent about "duration" method parameters

[Stephan202]

The AttemptTimeLimiters and WaitStrategies classes have methods that take a (long, TimeUnit) pair, whereas StopStrategies#stopAfterDelay accepts only a long. Not a big deal, but slightly unfortunate from an API point of view.

How about aligning StopStrategies with the other two classes by introducing StopStrategies#stopAfterDelay(long, TimeUnit) and deprecating StopStrategies#stopAfterDelay(long)?

(I understand the some of the strategy interfaces also take only a long, but most users will not implement those themselves, and in any case those types are in some sense more "low level".)

[rholder]

I like consistency, too. That's a good catch. Feel free to open a PR for it, and I'll get it into the next release.

[Stephan202]

Cool. I opened PR #39.

[rholder]

Your duration method parameter consistency fix should be good to go now in 2.0.0. Thanks again for your contributions.