WAITP-1122: Update users import

[tcaiger]

Issue #: WAITP-1122: Update users import (gender and verified)

Changes:

• Include the ability to import with no gender OR have an 'unknown' option
• Include the ability to import as 'verified'

---

[rohan-bes]

Just a suggestion to use @tupaia/types over re-defining the enum options for verified_email

[rohan-bes]

Suggested change

	verified_email: [constructIsEmptyOr(constructIsOneOf(['unverified', 'verified', 'new_user']))],
	import { UserAccountSchema } from '@tupaia/types';
	...
	verified_email: [constructIsEmptyOr(constructIsOneOf(UserAccountSchema.verified_email.enum))],

This is fairly new functionality, but now we have a package called @tupaia/types which we use to maintain a source of truth about our models. It's possible we could replace all these validators in central-server with ones that use ajv and @tupaia/types but for now I think we can at least rely on them for enums and the sort.

@IgorNadj I feel you've got a stronger grasp on using @tupaia/types that I do, does what I'm suggesting here seem appropriate?

[IgorNadj]

Ah yep, here's an example of using an enum:
https://github.com/beyondessential/tupaia/blob/dev/packages/central-server/src/apiV2/utilities/constructNewRecordValidationRules.js#L292

[tcaiger]

Nice, this is great. I have added the type for verified email but the type for gender is just a string so I've left that one as is.

[rohan-bes]

Awesome! Thanks @tcaiger