Refactor/user selection level

[theodorklauritzen]

MERGE #406 first!

This PR adds different levels of fields to expose from the user object. This should hopefully reduce the amount of user data that is exposed.

[JohanHjelsethStorstad]

I think it is more correct to use Prisma giving it the selection to generate the types, however, I still think the types for all different selections is sort of clucky. Ideally, I think all reads should have a filterSelection (an includes) to be as explicit as possible. -> this filter has a name (I belive we probably should call them selections as it is consistent with SELECT) and this name always corresponds to a type by Prisma.UserGetPayload. This type should have the same name... . I am sort of wondering, why do we need the type? can't we have a wrapper takin in the selection object you want to use. So if you need the UserNameFiltered type you use SmartWrapperName or with som name changing Selection

[Paulijuz]

whops, trykket knappen med et uhell. bare å ignorere