Fix incorrect flag in token refresh flow

[dareste]

When refreshing tokens for an existing session, the code is storing session data to the wrong variables (new_session, new_access_token, new_refresh) instead of updating the existing session variables (session_jwt, access_token, refresh_token).

As a result, the existing session does not get the updated tokens, the session continuity breaks and the user is forced to re-authenticate.

The fix is to set isNewSession to false when calling storeSessionDatain the refresh flow.

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[dareste]

I have hereby read the F5 CLA and agree to its terms

[route443]

Hi @dareste thanks for reporting! This is a serious issue that appeared after the #108. I added CI and a test that specifically verifies this behavior to prevent it from happening again in the future.