GREG-292: search for person via v1-api

See merge request !348

Switch text from National to Norwegian

See merge request !354

Calling norwegian fnr "National ID number" makes people input their id
numbers from their home country in addition to their passport numbers.

This text change hopefully makes it clearer for our non-norwegian
friends.

Only email sponsor when action is needed

See merge request !352

We no longer email sponsors(hosts) if they don't need to verify any of
the information provided by their guest.

Allow empty gender field in admin interface

See merge request !350

Add a possibility to search via v1-api, and add birth date to the data in such a case. No changes for previous gui-endpoint.

GREG-286: Update IGA check for UiB

See merge request !346

Allow page size to be configured in the request

See merge request !347

Fixes formating error for coverage report due to new gitlab version

Switch forms to onTouched mode

See merge request !343

GREG-244: Adding search in sponsor overview

See merge request !344

GREG-264: Remember gender when clicking back in wizard

See merge request !345

Show identity info on guest info page

See merge request !341

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

Fix bug in user info fetching on invite page

See merge request !342

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.

Fix problems with submit button not being disabled and some UX improvements

See merge request !339

GREG-255: Doing some changes on the edit role screen

See merge request !325

The intention of the setup is to trigger a new call to userinfo after an
invite has been used to start a session in the backend. This is done by
checking a state value. Due to an oversight we did not watch the state
value itself, but instead the function used to updated it, which
obviously does not change.

Resolves: GREG-276