Issue: GREG-240

Since we may not want to enable the identity check, it must be
togglable. This commit adds environment variable
REACT_APP_ENABLE_IGA_CHECK for toggling the check in the frontend, and
django settings variable IGA_CHECK for toggling the check in the
backend.

Relabel the invitation resend button to make its purpose more clear.

Adding a role without selecting either of these makes no sense, and will
be refused by the backend accordingly.

Displays a warning if the identifier the sponsor wants to verify is
already assigned to someone in the IGA, or if the backend could not
contact the IGA to check.

Switches from using a Controller to the simpler uncontrolled setup.
Label has been set to be permanently shrunk since mui refuses to realise
that the field has input when using rhf's setValue.
Validation now happens onChange, alerting the user while typing.
Submit button is disabled if you have not touched the field and when the
content of the field is an invalid email. After submissions, the new
value is treated as the default, disabling the save button until the
field has been touched again.

Resolves: GREG-196

Andreas Ellewsen authored 3 years ago and Jonas Braathen committed 3 years ago

If a sponsor verifies a nin that is already in use by an account in
cerebrum, the guest will gain access to that account, which in turn
allows the guest to change the password of that account. This makes it
possible to abuse the guest service to steal the account of users.

A feature that checks for this problem, and helps the sponsor make a
decision on it, will be introduced in the near future. At that point
nin verification can be enabled again.

Resolves: GREG-202

It turns out that different institutions have different criteria for
what counts as good enough papers to verify an Norwegian National
identity number. This commit makes it possible to specify different text
for each language option for each instance.

Resolves: GREG-199

Resolves: GREG-200

Values of fields now show the current dates of the role after data has
been fetched, instead of the placeholders.

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