refactor(organizations): add of useSession hook TASK-1305

[pauloamorimbr]

👀 Preview steps

No behavior will change with this implementation, but it can be tested by using the new hook somewhere.
As a test I've modified MyProjectRoute to verify that currentLoggedAccount was properly dispatching component re-render and that using hooks methods are working properly as well:

...
export default function MyProjectsRoute() {

  const [counter, setCounter] = React.useState(0);

  const {currentLoggedAccount, refreshAccount} = useSession();

  useEffect(() => {
    setCounter((prev) => prev + 1);
  }, [currentLoggedAccount]);

  return (
    <>
    <button onClick={refreshAccount}>Refresh {counter} - {currentLoggedAccount?.username}</button>
    <UniversalProjectsRoute
...

Result:

💭 Notes

• This PR adds the useSession hook, aimed to be used instead of the current sessionStore class to access the session data and methods.
• The useSession hook returns the currentLoggedAccount user, which is already filtered to be an existent account returned from the /me endpoint and verified not to be an anonymous account, which is currently done in several places around the codebase where the currentAccount from sessionStore is used.
• The internal implementation of this hook will eventually migrate to use react-query, keeping the hook's signature.
• This implementation can be used as a base for the migration of the other existing stores to allow for future dropping of mob-x in favor of using react-query to cache data.
• First usage of this hook can be seen in refactor(organizations): code cleanup and patch data cleanup in account settings and tos view TASK-1292 #5290

[Akuukis]

LGTM, not tested. Very useful for migrating away from reflux/mobx!