DBP: Implement exponential backoff for optout retries

[jotaemepereira]

Task/Issue URL: https://app.asana.com/0/1204006570077678/1207370913988488/f
Tech Design URL:
CC:

Description:
Implement exponential backoff for opt-out retries

Steps to test this PR:

1. Run opt-out operations that you know will fail; you can add some manual code to make them fail if you want to. Or just throw in the CaptchaService endpoints for example.
2. Then run queued operations. After finishing running, check that every time the preferredRunDate is set after the opt-out fails, it respects the exponential calculation depending on the number of failures. It should never pass the retryError limit on the broker JSON file (at the moment is 48 hours for all brokers)

[aataraxiaa]

I tested this using the following steps:

1. Added a log statement to calculateNextRunDate
2. Ran a profile scan
3. Ran opt-outs via debug menu

I didn’t run queued operations, as I think running the opt-outs confirms the expected behavior, but please correct me if I am mistaken @jotaemepereira. The log output was the following, which seems to indicate correctness:

PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 5, NEXT DATE: 115200.0
PAST TRIES: 5, NEXT DATE: 115200.0
PAST TRIES: 6, NEXT DATE: 172800.0
PAST TRIES: 6, NEXT DATE: 172800.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 7, NEXT DATE: 172800.0
PAST TRIES: 7, NEXT DATE: 172800.0
PAST TRIES: 8, NEXT DATE: 172800.0
PAST TRIES: 8, NEXT DATE: 172800.0
PAST TRIES: 9, NEXT DATE: 172800.0
PAST TRIES: 9, NEXT DATE: 172800.0
PAST TRIES: 10, NEXT DATE: 172800.0
PAST TRIES: 10, NEXT DATE: 172800.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 11, NEXT DATE: 172800.0
PAST TRIES: 11, NEXT DATE: 172800.0
PAST TRIES: 12, NEXT DATE: 172800.0
PAST TRIES: 12, NEXT DATE: 172800.0
PAST TRIES: 13, NEXT DATE: 172800.0
PAST TRIES: 13, NEXT DATE: 172800.0
PAST TRIES: 14, NEXT DATE: 172800.0
PAST TRIES: 14, NEXT DATE: 172800.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 15, NEXT DATE: 172800.0
PAST TRIES: 15, NEXT DATE: 172800.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 1, NEXT DATE: 7200.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 2, NEXT DATE: 14400.0
PAST TRIES: 16, NEXT DATE: 172800.0
PAST TRIES: 16, NEXT DATE: 172800.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 3, NEXT DATE: 28800.0
PAST TRIES: 17, NEXT DATE: 172800.0
PAST TRIES: 17, NEXT DATE: 172800.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 4, NEXT DATE: 57600.0
PAST TRIES: 5, NEXT DATE: 115200.0
PAST TRIES: 5, NEXT DATE: 115200.0
PAST TRIES: 6, NEXT DATE: 172800.0
...

So, based on my understanding of expected behavior and these results, approving. However, as I said @jotaemepereira, please correct me if I missed something.

[Bunn]

LGTM, small rename comment

[github-actions]

This PR has been inactive for more than 7 days and will be automatically closed 7 days from now.