Opaque tokens

[jonbarrow]

Resolves #107 and #108

Changes:

Moves tokens to random data instead of storing the data directly. Trying to fit all the data inside the token was a losing battle because of how space-limited it all ways. This removes clients abilities to handle data entirely locally, but that's fine since it's only a single network hop. I made the tokens be the length of what they are from the official sources, despite the fact that some can sometimes be bigger, just to keep things simple

Marking as a draft because this isn't finished. The entire gRPC side needs to be done, which relies on PretendoNetwork/grpc#10 being merged. Also for gRPC, I think we should just ditch the v1 implementation entirely since it's token handling is fundementally incomaptible with this new handling. Just cut our losses there

• I have read and agreed to the Code of Conduct.
• I have read and complied with the contributing guidelines.
• What I'm implementing was an approved issue.
• I have tested all of my changes.

[mrjvs]

I haven't checked token sizes in my review, will possibly need to be checked by someone else

[jonbarrow]

This should be ready for review now. I did test that it builds locally and it does, though not much else. It should all work fine though, the changes just replace manual token handling with DB lookups so nothing huge really

I'm not going to be here tomorrow however, so do feel free to make any required bug fixes/changes while I'm out just to push things along

[DaniElectra]

This comment is inaccurate, there isn't any title ID in use here, this should be about client ID / client secret