To prevent the invite id from showing up in various logs along the way,
we change to use an anchor in the invite url, and a post request to the
backend.

Invite links are now on the form /invitelink/#<uuid> and the frontend
redirects to /invite as usual after the session has been created.

Resolves: GREG-90

Code for guest routes moved to their own folder so that we don't need
multiple api calls.
Serializer class for roles has been simplified with methods for
validation of each field and a separate one used in invites without
requiring the person field.

Resolves: GREG-61

Allows search using e-mail and mobile phone, limiting results to 10
first matches

To make handling info about roles and persons easier we split them into
separate objects. The Profile page has now gotten its own api endpoint
where a sponsor has access to all guests instead of only those they are
sponsor for which is used on the sponsor frontpage. This is necessary
since a sponsor may want to give a role to someone they are not
currently sponsor for.

- Introduces the Invitation and InvitationLink models for keeping track
  of guest invitations and the links connected to them.
- Adds a post endpoint accessible by sponsors to create invitations for
  guests.
- Adds a get endpoint for the guests to review their invitation
  information.
- Adds a post endpoint for the guests to confirm their invitation with
  updated mobile_phone number if they want.
- Removes token field from Person since it is not used.