Your checklist for this pull request

• I've read the contributing guideline.
• I've tested my changes by building and running the project, and testing changed functionality (if applicable)

What is the current behaviour?

Multiple MWDB users are reporting problems with unexpected session expiration during normal usage or after leaving the MWDB opened for a longer time.

This is pretty annoying and is caused by few flaws in client-side code that handles authentication.

What is the new behaviour?

This PR applies few fixes:

• Webapp periodically refreshes the session to prevent expiration when tab is opened for a longer time. Unfortunately, that mechanism caused the opposite effect, because there are huge chances that some of /api/refresh requests will fail after multiple periodic calls, causing the logout. Changed handling of that situation from logout to silent error reported in console. If session has really expired, user will be notified anyway via HTTP 401 handling.

• There was a race-condition on mount: some API requests were sent on component mount before the authorization token is set in Axios request headers. That situation results in HTTP 401 and logout even if correct session token is available in localStorage. Added useAxiosEffect to setup interceptors and headers as a part of initial render (like componentWillMount), so Axios will be set-up first.

• getStoredAuthSession haven't checked for empty user key in localStorage, which results in error reported in dev console. Added proper check.

Test plan

• Check if problem is fixed and there is no regression