Use linear backoff on the SDK v3 Waiter due to failure rate for short…

[Ic3w0lf]

… running tasks

What it solves

Since v3 the AWS SDK uses a Waiter with exponential back-off and jitter to check for the state of the task. This is in general a good thing, as it reduces the load on the AWS API and is more efficient.

HOWEVER:
If the task that is started is short-lived, the Waiter might not be able to catch the task in the "RUNNING" state at all, because the potential back-off method will increase the delay to a value that is too high.

The Waiter will randomly catch it in the "STOPPED" state and throw an error as the exit code is not checked in the waiter. To combat this we use the old behavior, we will go back to use the linear back-off by setting both delay values to the same value.

See: https://aws.amazon.com/blogs/developer/waiters-in-modular-aws-sdk-for-javascript/

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• Pull request title is brief and descriptive (for a changelog entry)

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, or enhancement
• Label as bump:patch, bump:minor, or bump:major if this PR should create a new release

[github-actions]

🏷️ [bumpr] Next version:v4.1.0 Changes:v4.0.0...geekcell:linear-backoff

[github-actions]

🚀 [bumpr] Bumped! New version:v4.1.0 Changes:v4.0.0...v4.1.0