Add JWT middleware and me query

[KillerX]

The middleware is applied to all requests. If the Authorization header is not set the request is marked as Anonymous.
The middleware is not responsible for preventing access, it is only supposed to validate the token (if it exists) and extract claims into the context. Claims retrieved from the context later can thus be considered valid and used to Authorization purposes.

[fredrikvedvik]

Do we want this to be called personId? One could argue that this is a bad naming originally in Members...?

I'd either go with "id" or "userId".

[fredrikvedvik]

Of course if this is just a "forward" of what we get from auth0, then we don't have much of a choice

[KillerX]

Yeah, I'll move this to ID, makes more sense, even if members i "wrong".

[andreasgangso]

I'm curious if we need to check hasMembership.
I've never done that
https://github.com/bcc-code/bcc-code.github.io/blob/master/_docs/signon/openid-connect.md
edit: those docs are for idtoken but the accesstokens have that as well
"https://members.bcc.no/app_metadata": {
"personId": 12345,
"hasMembership": true
},

[KillerX]

I'm curious if we need to check hasMembership. I've never done that https://github.com/bcc-code/bcc-code.github.io/blob/master/_docs/signon/openid-connect.md

I will use this for https://github.com/bcc-code/brunstadtv/pull/21/files#diff-fcaa1411fa7893dd366fed7c9738f2dc0b054503ed682c3df089fbd7946155b0R22 thanks