useAccount, useLogin, useLogout

[mpinter]

Struggled a bit with the original approach with getAccount, so in the end changed the following:

• the api requests must receive the jwt token from outside
• the token is accessed only from React context via useLocalStorage - this way everyone listening on the local storage content is notified when it changes. Today we're really accessing it only in single place, but I want to avoid any weird bugs caused by the storage and the react state desyncing

The useCityAccount hook (now renamed to useCityAccountAccessToken to be more explicit) should now serve as a the single source for the accessToken only.

The useAccount hook should be a good example how to use this approach to gather any data which stand behind auth.

---

Also replaced msal usage for these hooks everywhere, kept the msal setup in in case we need to authenticate against the old provider somewhere in the migration process

[github-actions[bot]]

:partying_face: Bratiska-cli successfully created an kustomize file.

:partying_face: Bratiska-cli successfully built an image from path: . :partying_face: Bratiska-cli successfully created an kustomize file. :partying_face: Bratiska-cli successfully built an image from path: . :partying_face: Bratiska-cli successfully created an kustomize file. :partying_face: Bratiska-cli successfully built an image from path: . :partying_face: Bratiska-cli successfully created an kustomize file. :partying_face: Bratiska-cli successfully built an image from path: .