Description

The current names for retry policies exported from the package are not very accurate at describing what they do. Let's make it a little easier.

Specifically, retryForeverExponentialCapped doesn't make sense because the maximum timeout that can be reached is about 17 minutes, so the 30 minute cap is meaningless.

Let's simplify these to the following:

Notable, the "about" word is helpful for showing that the randomize option is being used. Also notable, the forever option is not being used, so that errors that retry don't stay "stuck" in a retry loop. This may cause more errors to be seen, but that is likely a good thing so that developers can find issues in their apps.

The tenRetriesInAboutThirtyMinutes policy looks like this:

{
  retries: 10,
  factor: 1.96821,
  randomize: true,
}

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.