Backport Geo: Dynamic Backoff strategy to 9 2

What does this MR do?

Backports !2128 (merged) to %9.2

Are there points in the code the reviewer needs to double check?

No, code is compatible with %9.2 codebase

Why was this MR needed?

There are customers being hit by this, see !2128 (merged) and gitlab-ee#2639

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

• !2128 (merged)
• gitlab-ee#2639