api, ui: Implement refresh token

[SamuelPull]

• The feature was discussed based on security audit findings and current best practices
• I have searched the issues of this repository and believe that this is not a duplicate.

Description 💡

• Create a new api route for token refreshing (/refresh) This route will take the refresh token, verify it, and if it's valid, issue a new access token (token cookie)
• Update login route(s) to issue an access (token) and refresh (refreshToken) tokens.
• Since we are using httpOnly cookies, api server needs to send expiration date(s) of the tokens in response,. Client can store it in-mem or so and check expiration before making a request. If the token is expired, the client requests a new token from the server. (TBD does this change require new apiVersion?)
• Implement checking the expiration date and refreshing token in frontend
• Update e2e tests
• Update documentation
• Should we use short lived tokens, or implement token blacklist? With blockchain, it's hard to say what will a blacklist's impact on performance be.
  EDIT:
• API: remove groups data from token #1755

EDIT 2:
I'm not sure if there is any added value in implementing refresh token without token rotation and/or option to revoke refresh token, but blockchain is not an optimal data store to handle this added complexity. On second thought, I don't think this adds value to the users and partners at the moment.

[SamuelPull]