profile: show warning and option to reactivate when contact method is disabled

[Forfold]

• Identified the issue which this PR solves.
• Read the CONTRIBUTING document.
• Code builds clean without any errors or warnings.
• Added appropriate tests for any new functionality.
• All new and existing tests passed.
• Added comments in the code, where necessary.
• Ran make check to catch common errors. Fixed any that came up.

Description:
This PR adds a warning to a contact method if it is currently disabled. The warning icon should have a tooltip directing the user on how to reactivate said contact method.

Additional Info:
This PR also refactors the verification form/dialog to use React hooks, as well as updates the verification mutations to use our latest graphql library.

[Forfold]

Tests passed.

[Forfold]

Comments addressed. Outstanding work is to create a new migration for the user_verification_codes table to:

• Remove user_id and contact_method_value columns
• Add a contact_method_id column
• Replace send_to with a bool sent

[arurao]

A few things I noticed by functionally testing the PR:

• Should we add a validation for checking if code entered on UI only consists of numbers and of length 6? Right now, if we enter a string, it goes all the way to the backend and returns unexpected error. It would be better if we avoided it going to the backend and masked the error with some helpful text too.

This is what we see currently:

It would be nice to instead see a validation error similar to

• One nice-to-have validation we could maybe add is to disable the Submit button on the dialog unless the user has hit the Send code button at least once. What do you think?

• If a user has 2 contact methods, clicking on Verify/Reactivate for the first contact method shows the dialog for actually the second one.

[Forfold]

@arurao Looks like I forgot to change the type of the textfield to type='number' which would disallow typing anything but numbers. Thanks for catching, I will get this fixed

[mastercactapus]

Can you merge latest from master into this? Looks like there's a conflict.

OOO, comments were addressed