[PM-11476] Prevent parallel refreshToken calls

[Timshel]

📔 Objective

The goal of this PR is to prevent the clients from making parallel refresh token calls.
This can introduce issues if the provider is rolling the refresh token and invalidating the old ones after use.

This is simply done by keeping the Promise of the current refresh call as long as it's not finished and returning it again if another call is made.

Since I'm working with Vaultwarden I'm unsure how pertinent it is with the official server, but I believe it might make sense since it's probably way easier to handle in the client and not in the server.

First time I encountered the issue is with a refresh token validity set to 5 min or less (which the client consider expired then) which then trigger a flood to refresh calls which might result in invalidating the user session.
More recently someone had the issue with the browser extension and Authentik not liking receiving the same refresh_token twice.

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-11476

[Timshel]

Any feedback ?

[benedikt-bartscher]

Thanks @Timshel for the fix!

Is there anything contributors can do to get a faster review/feedback on this PR?

[derSoerrn95]

Anything new?

[trmartin4]

Hello! Thank you for your contribution. The team will be taking this into review soon, and we'll be able to perform a full assessment at that time and provide feedback on any required changes.

[Timshel]

Any news ?

[benedikt-bartscher]

@trmartin4 do you have a schedule for this PR review?

[trmartin4]

@Timshel thank you for checking in. We have pulled this into our next sprint for review, so it should be soon. Thank you for your patience. We realize that this has been open for a while, but the team has had to balance a lot of different priorities in the interim.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Checkmarx One – Scan Summary & Details – 21490dee-fbf8-4315-84a2-e39ac08e9163

Fixed Issues (1)

Great job! The following issues were fixed in this Pull Request

Severity	Issue	Source File / Package
	Client_Privacy_Violation	/libs/tools/generator/components/src/username-generator.component.html: 3

[Patrick-Pimentel-Bitwarden]

No issues foreseen with this code change. Tested locally the refresh token and the flow seems fine and nonbreaking.

[Patrick-Pimentel-Bitwarden]

Handing this off to our QA team to finish the review process.

[Patrick-Pimentel-Bitwarden]

Just passed through QA with all ✅

Thank you so much for taking the time to contributing. This should be rolled into our next release.

[derSoerrn95]

Great 😍! Thanks @Timshel

[Timshel]

@Patrick-Pimentel-Bitwarden thank you :)