feat: implement skipping backoff strategy

[daveleek]

Description

Implements a backoff strategy for metrics and features endpoints based on skipping scheduled polls/posts.
Specific failed request responses (401, 403, 404, 429, 500, 502, 503, 504) increases amount of requests to skip.
10 skips in a row is maximum.
401, 403, 404 cause the skip counter to increase to 10 immediately

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Unit tests to provoke the behavior has been added

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[sighphyre]

Just looking at the test name, I don't see a check for responses == 10? Is that intentional? Am I reading the test wrong?

[daveleek]

Yeah can't check it directly, so there's a loop of 10 in there along with a check that call count hasn't increased as a result of that loop - indicating it went straight to skipping 10, and then the additional invocation that should be let through the skip check and increase call count by 1

[sighphyre]

Don't know the feature very well but overall I think this LGTM. I would probably wait for a review from someone who's actually implemented this one tho

[chriswk]

55?

[chriswk]

oh, right SUM(1..10) for the skips.

[chriswk]

Nice. Looks recognizable :)