DCMAW-10829: Enhances http request retry strategy with exponential backoff and full jitter

[jmooney-dd]

​DCMAW-10829

What changed

• sendHttpRequest:
  • Updates retry policy with exponential backoff and full jitter
  • Updates interface to use Result pattern after discussion feedback here
• Updates functions that consume sendHttpRequest as interface has changed:
  • getBiometricToken
  • publicKeyGetter (I made 2 additional changes listed below here we can revert if we want as minimal change as possible here):
    • Updated func in publicKeyGetter to use the Result pattern instead of throwing errors some of the time cb1e74c2c47ae5847b9ca6db848c01bebd040a33
    • Updated publicKeyGetter to handle parsing error explicitly 8b3852d001eccaae9b2175b4687a736ae41da8c3
    • Update error message when response body does not match the expected JWKS structure f3e03f2f916fecf11db31fa26f3bb312f7c0ee2f

Why did it change

Exponential backoff

Reduces load on target server giving it time to recover while gradually increasing the interval between retries

Full jitter

Prevents synchronised retries which can overwhelm the target server by altering the delay between retries by a random amount

Sonar security hotspot

Status

Resolved - Akin has resolved the hotspot: https://gds.slack.com/archives/C060PANF03T/p1737366725133829

Summary

Sonar flagged that we are using a pseudorandom number generator and asks we check it's safe to use here. We are using it to calculate a jitter value.

Link to hotspot

​Evidence

Deployed stack and ran api tests - all passing

Checklists

• There is a ticket raised for this PR that is present in the branch name
• No PII data logged. See guidance here
• Demo to a BA, TA, and the team.
• Update README with any new instructions or tasks

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud