feat: rewrite permission logic to no permissions having lowest priority

[gdiepen]

Instead of giving NO_PERMISSIONS a higher priority than all the other priorities, which allows for weird blocking of access if you have both MANAGE PERMISSIONS as well as NO_PERMISSIONS, this PR will modify the permission logic to be giving you the access of the highest allowed permissions based on the default permission, your user permissions, as well as each of your groups permissions.

In order to check what the type is that gave you access, we start with type fallback, then if the user permission prioerity is strictly higher than the fallback one, we change the type to user and if after that any of the group permissions have a strictly higher priority, we consider the group to be the type that granted this access.

For example, if the default permission is READ and your user also has explicit READ permissions, we consider the type to still be fallback (the fact that the user has read access does not grant anything additional above the defaults).

By using this logic and assigning NO_PERMISSIONS the lowest priority, you automatically solve the problem that if you are a member of two groups and one group gives you MANAGE access and the other one NO PERMISSIONS, you end up with no permissions in the current state (in the state with this pr, you would end up with MANAGE).

Because of the changes in this PR, this also Implements #80

This also might address #83, though without the use of an extra config variable