chore: refactor cache client auth flow

[Harasz]

Description

Contributor checklist

• [x] Breaking changes - check for any existing interfaces changes that are not backward compatible, removed method etc.
• [x] Documentation - document your code, add comments for method, remember to check if auto generated docs were updated.
• [x] Tests - add new or updated existed test for changes you made.
• [x] Migration guide - add migration guide for every breaking change.
• [x] Configuration correctness - check that any configuration changes are correct ex. default URLs, chain ids, smart contract verification on Volta explorer or EWC explorer.

[Harasz]

It does not matter in my opinion. The execution of the failed request is manged by the code itself. We are operating in the same context of the promise. So if we have something like this

await update(1);
await update(2);

and update 1 will fail, it will try to run it 3 times and eventually it will fail, but update 2 will not execute, bc first update throw an error. So from the code perspective its the same promise that needs to be fulfilled.

@jrhender

[Harasz]

@JGiter hymm, it would be great, but i dont think it's possible :/

[artursudnik]

Have you considered using Axios interceptor to implement retrying failed requests?

[Harasz]

@artursudnik request interceptor is only accepting axios config, so i can't override promise there. I can use response interceptor and catch errors, but it's not an ideal approach in my opinion.

[ewf-devops]

:tada: This PR is included in version 6.0.0-alpha.29 :tada:

The release is available on:

• npm package (@canary dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[ewf-devops]

:tada: This PR is included in version 6.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: