oauth2: HTTP Auth method oauth2 does not replace the last refresh_token with the new refresh_token
When the HTTP Auth action using oauth2 uses a previously stored refresh_token to refresh both the access and refresh tokens, the auth server returns new access and refresh tokens, but tasker is not replacing the old refresh_token with the new refresh_token. Tasker continues to use the older refresh_token, which technically has not expired, but the server side deletes the older refresh_token since the server knows it just issued a new refresh_token.
When tasker subsequently tries to refresh the access token, it uses the older, no longer valid, refresh token and, of course, authentication fails.
The oauth2 spec is long and complex, so I am not claiming tasker is wrong since that older refresh_token technically hasn't expired when the problem occurs, but I have observed that every other client implementation of oauth2 I've encountered does indeed start using the new refresh_token so it would be helpful if tasker did as well.
Tasker version is 5.10.1