Refresh auth flow does not trigger stories auth refresh

[RichDom2185]

For some reason, if the currently logged in user expires and is automatically redirected to the login page, after logging back in, the query sent to [stories backend URL]/user does not include the currently logged in course ID query parameter, resulting in a 400. This happens even after a refresh.

The only fix for now seems to be force refreshing, which may or may not hint at something to do with the local storage.

[RichDom2185]

@chownces I think trying to fix this is like trying to patch a sinking ship, we should not be doing all these fixes in the frontend but instead create a separate auth service so that the microservices implementation is transparent to the frontend and the frontend only needs to contact one auth endpoint which will authenticate with both backends.

What do you think?