It has been decided that a sponsor at a unit should have access to all
roles at that unit. This includes all units accessible through
hierarchical access.

Resolves: GREG-150

Dates can now be changed after they have started and ended. This means
that there is no situation which needs disabling the input fields, and
disabling has been removed.

Start and end date can now be in the past. The following rules apply:
 - Start dates can be any date in the past, and no more into the future
   than the max days property of the role type.
 - End dates follow the same rules
 - End dates must be equal to or later than start date.

Notification publishing has been reviewed to ensure duplicate
notifications are not created when start or end date is today.

Resolve: GREG-148

- Combine the /invite and /invitelink endpoints into one
- Return error messages from the backend
- Handle errors in the frontend
- Lower number of queries ran when calling the userinfo endpoint

Used to "log" a user out in the manual invite flow

Serialization has been moved to serializer classes, sharing them when
sensible and Views have been converted to ViewSets to simplify code.

Separates the queryset and the serialization from each other.

The OU view deserves its own file, and the guest info is actually a
person view and should live with  the other person views.

The profile page of a guest now shows a verification button if the guest
has a passport or national identificaiton number that has not been
verified. Clicking the button shows a dialog, with a confirmation button
which triggers a PATCH request to the backend and reloads the page when
it returns.

Resolves: GREG-101

Does the same as before with less and more readable code.

Any user that does not have a GregUserProfile must be a superuser so
this is not a problem per se, but it should be handled. For now we
simply treat them as an anonymous user and deny access.

Resolves: GREG-116

Start dates can now be blank, check for correct sponsor has been moved
to the more appropriate validate method and we now check that the role
exists before doing anything in the serializer

If the user is neither a guest or a sponsor, generic text explaining
this is shown. If they are a guest, they are shown the data related to
them. If they are a sponsor, they are redirected to the /sponsor/ route.

Resolves: GREG-97

To prevent hammering on the invite endpoint we throttle requests to the
endpoint to 100/day per ip.

Resolves: GREG-84