fix: Ignore email and phone assertions when token hash is being verified

[Dastaan2k]

Supabase Docs

Following the above link, verifying token hash from magic link doesn't require email or phone in request body
(only 'token hash' and 'type' is required in the js example)

Pre commit state of the code threw assertion error if neither email nor phone is present in verifyOtp call preventing users to verify token hash without passing email or phone in request body ("auth/verify" endpoint called inside this function throws an error as well if email or phone is passed in request body along with token hash and type)

Hence have added a condition that will ignore the first email and phone assertion if token hash is populate

[Vinzent03]

Thanks for your contribution!