Add authenticated session to app server context

[apedroferreira]

Add authenticated session to server context so that it can be retrieved in custom functions.
Had to move some things around between @mui/toolpad-core and @mui/toolpad-utils, let me know if it could be set up differently.
Also updated docs with an example, and covered in tests.

[apedroferreira]

Looks like with the recent changes we can redirect to the sign-in page with React Router: 172d2c3

About the flaky Firefox test mentioned in #3179 (comment) I just added those console errors to the ignore list in this test, i think it should be fine to do that?
From what I found it looks like in the checks that see if the user gets redirected to the sign-in page, that redirect interrupts some network requests and in Firefox that leads to showing some console errors. This discussion seems to be related to that https://bugzilla.mozilla.org/show_bug.cgi?id=1280189#c7, and seems like they're just browser differences...

[Janpot]

• Let's add a separate table for this interface?
• Would it make sense to call this session instead of user?

[apedroferreira]

session sounds good, it's what it's called in @auth/core too, user might be a bit too generic.

[apedroferreira]

I've made these changes, ended up having session in context which has a user property with this data.
Also covered this in one of the authentication tests (since the user needs to be logged-in to see the context session data).

[Janpot]

@apedroferreira Would it make sense to also add user info in the page state for components to bind to? e.g. like https://docs.retool.com/reference/apps/global/objects/current_user

[apedroferreira]

@apedroferreira Would it make sense to also add user info in the page state for components to bind to? e.g. like https://docs.retool.com/reference/apps/global/objects/current_user

It would be nice, I've created an issue #3209.
Marked it as a good first issue but not 100% sure if I'm underestimating how difficult it would be.