How user verification works in FusionAuth: Version 1.59 changes

FusionAuth has updated its user verification system as of version 1.59, introducing separate verification processes for email and phone numbers while deprecating the old system that relied solely on email. The new approach involves the use of individual user identity objects, each capable of being verified independently, with verification statuses stored in fields like `verified` and `verified_reason`. This update allows for more nuanced verification criteria, such as marking users as verified if they were imported from external sources or deemed trusted by administrators. The system also supports phone numbers as primary identifiers, offering a similar verification process to that of email, involving sending links or codes for users to confirm their identities. Registration verification has been removed to simplify the process, and new API functionalities have been introduced to accommodate these changes, offering more flexibility in managing user verification programmatically.