Better error messaging when the generic execute/async overloads are used on a non-generic cache policy, and the sync/async usage is not aligned between policy and execute call.

Remove references to deprecated overloads in readme

Add notes on when retry and circuit-breaker rethrow exceptions

To add the error count to the onRetry actions

…thCount

Eliminates recursive calls which would lead to StackOverflowException. Reduces the number of method-chain hops for certain overloads.

Adds specs on new WaitAnd/RetryForever/Async(...) overloads where the onRetry/Async delegate can take the retryCount as an input parameter.

…-overloads

Add new retry forever / wait and retry forever overloads where the `onRetry` delegate can take `retryCount` as an input parameter.

Fix: generic execute method on non-generic CachePolicy should not throw internally when cache holds no value under the given cache key

… similar cases

Minor tidying and consistency in the timeout syntax classes

Minor tidying and consistency in the timeout syntax classes

Rationalise timeout tests for 338 (make the only new tests those which specifically test the new functionality)

Fix Context.PolicyKey such that, as execution bubbles back outwards through a PolicyWrap, Context.PolicyKey correctly adopts the value of the policies in play during the outward journey through the wrap.