feat(gotrue): Add phone mfa enrollment

[dshukertjr]

What kind of change does this PR introduce?

feature of adding phone support for MFA enrollment

JS PR here: supabase/auth-js#932

What is the current behavior?

Enrolling in MFA via SMS is supported .

What is the new behavior?

SMS MFA is not supported.

[coveralls]

Pull Request Test Coverage Report for Build 15482416459

Details

• 25 of 32 (78.13%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.06%) to 75.345%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/gotrue/lib/src/types/mfa.dart	10	17	58.82%

Files with Coverage Reduction	New Missed Lines	%
packages/gotrue/lib/src/fetch.dart	1	91.36%

Totals
Change from base Build 15425969446:	-0.06%
Covered Lines:	2894
Relevant Lines:	3841

---

💛 - Coveralls

[dshukertjr]

I know this isn't great, but I think we can call it that it's a fix. Open to suggestions to avoid this though.

[grdsdev]

See my comment in https://github.com/supabase/supabase-flutter/pull/1188/files#r2131807418

[grdsdev]

Lets validate that an issuer needs to be provided for the totp factor type also.

Suggested change

	if (factorType == FactorType.totp) {
	body['issuer'] = issuer;
	} else if (factorType == FactorType.phone) {
	if (phone == null) {
	throw ArgumentError('Phone number is required for phone factor type');
	}
	body['phone'] = phone;
	}
	if (factorType == FactorType.totp && issuer != null) {
	body['issuer'] = issuer;
	} else if (factorType == FactorType.phone && phone != null) {
	body['phone'] = phone;
	} else {
	throw ArgumentError('Invalid arguments, expected an issuer for totp factor type or phone for phone factor. type');
	}