Split a function into two

In D10150#295223, @ashoat wrote:

This feels pretty messy. I'm not sure what the callstack looks like, but is it possible to introduce a second function for this (with shared code factored out) instead of overloading fetchPrimaryInviteLinks to handle two different scenarios?

Rebase

Rebase

Use a param object instead of two args for hash and holder to avoid the confusion between them

Accepting without review. What procedure did you use to rename all the types?

on the first rehydration this value could be undefined

Is it also true for other values from the keyserverInfo? Should we also handle them somehow?

Is the default_role column nullable at this point?

Use better error code

Rebase

Rebase

Move encrypting inside try-catch block