feat: sponsored sbtc txns

[alexp3y]

Try out Leather build dc94e36 — Extension build, Test report, Storybook, Chromatic

@fbwoolf @kyranjamie @markmhendrickson Ready for review. Covers sponsorships for both contract calls and swaps. Need to change API URL config once in place. Will update shortly once updated testing APIs are online.

@fbwoolf I removed the swap sponsorship condition checks from here (other than feature flag enabled) to rely solely on the API verification rules (gives us a bit more flexibility in updating sponsorship rules).

[kyranjamie]

Could this be discriminating union to help types when consuming?

Suggested change

	interface SbtcSponsorshipVerificationResult {
	isVerifying: boolean;
	result: SbtcSponsorshipEligibility | undefined;
	}
	interface SbtcSponsorshipVerificationResultPending {
	isVerifying: false;
	}
	interface SbtcSponsorshipVerificationResultVerified {
	isVerifying: true;
	result: SbtcSponsorshipEligibility;
	}
	type SbtcSponsorshipVerificationResult = SbtcSponsorshipVerificationResultPending | SbtcSponsorshipVerificationResultVerified;

[markmhendrickson]

@alexp3y is this testable with regular testnet?

[alexp3y]

@markmhendrickson If you bridged testnet sbtc, txs from that address should work. The current testnet API doesn't have whitelisted contract support, but any sbtc swaps / sbtc post-condition txs would work in theory. Will try to set up a separate test API now that works around not having testnet sbtc.

[markmhendrickson]

Presumably I should see sBTC in the list to test sponsored swaps?

[markmhendrickson]

I'm not seeing the enrollment transaction sponsored during testing on testnet:

[markmhendrickson]

Swaps need testing on mainnet, and testnet API will get updated to allowlist enroll transaction for further testing

[fbwoolf]

Found a small formatting bug created. I am pushing up a fix commit for now...

[fbwoolf]

@alexp3y I rebased this into one commit, but I didn't realize that would remove you as a contributor. Can you review the code and make a small commit change before I merge this into the feature branch? You can squash everything into a commit you make and push up?