Improve the tests.

When a sponsor creates a new guest invitation, and when a guest corrects their name
they must now use transcribed characters.

Instead of manually putting together the phone number and hoping we get
it right, we instead format the number using the phonenumbers library.
This library is already in use for validation, making it the obvious
choice. This means that the backend will only receive E.164 formatted
phonenumbers from now on. In addition, we now ensure that the number is
in fact a mobile phone number.

Sponsosr can now click a button next to passport/fnr values on the
guest info page to see the source and verifier of the value.

Resolves: GREG-275

By using onTouched mode validation does not complain about invalid
values until the users have changed focus from the field. Doing it this
way we don't complain about values until the user tries to use an
invalid one.

Does not work for all fields. For that to be the case, we will have to
do some clean up of controlled and uncontrolled values.

- added Autocomplete for easier fill out
- added function to concatenate strings for option label
- removed unused function getOuName
Issue: GREG-235

Comments and contact person had feature flags created for their
visibility some time ago, but we missed a couple of sections in the
frontend. In addition, comments that were set on a role during
invitation was invisible later, defeating the purpose. They are now
visible if comments are enabled.

Resolves: GREG-197

Necessary for OUs and RoleTypes with missing english or norwegian names

Resolves: GREG-177

Resolves: GREG-173

- Create a new loginbox component. To be used as invitation login
  latter.
- Add a util function that creates the correct stylized institution abbrevation

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

Issue: GREG-89

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.

Allows changes to start- and end date for guest roles. A new endpoint
has been added to the ui api for doing PATCH request to support this.
The max days of each role type is respected.

Resolves: GREG-83