Add vessel data structures for authentication

[madeline-os]

These data structures are based on previous solutions for authentication by @danbornside based on SubVessel (wrapped as AuthMapV) as well as Cale's idea for ErrorV which handles possibly failing queries in a way that does not expose incoherent behavior to the end-users. There is also an AuthenticatedV wrapper which glues together two view selectors which need have no relation to each other in particular, but the intended use case is to combine it with AuthMapV.

The handler provided for AuthMapV assumes that the result of the query does not depend on the specific identity making the query. This allows efficient aggregation of queries across different authenticated users. There are other sorts of authenticated queries which do depend on the specific identity, like querying for one's own profile. One way we can accommodate such queries is to extend AuthenticatedV with a third key for "Personal" queries which use AuthMapV but do not do query aggregation.

This PR should be updated once obsidiansystems/vessel#14 is merged.

[Yasuke]

LGTM, but I wouldn't mind seeing someone else rip into this one, as I don't do a ton of type work like this often!

[Ericson2314]

Per what I wrote in the chat, I think we are better off not bothering compose Compose, and just using :.:, until the base and base-orphans are fixed. That will make the version bumping of GHC and libraries we do easier at little cost.

[cgibbard]

@Ericson2314 Which chat? Also, what's the difference we're concerned about? There are some other places we're already using Compose...

[ali-abrar]

Thank you @madeline-os