OAuth token expiration is not handled by the UI and/or session manager

I noticed this when developing on osm-teams locally.

My oauth token expired, and the osm-teams api was returning responses like this when I used the api with a bearer token

`{"statusCode":401,"error":"Unauthorized","message":"Expired token"}`

So that seems correct. However, presently the osm-teams UI did not give any indication that anything was expired, even if I reloaded it:

Until I clicked on "create new team" which resulted in a 401 error json displayed in browser: