feat: introducing magic.link provider (email based authentication)

[aorumbayev]

Description

Please explain the changes you made here

• Adding integration with https://magic.link/ algorand extension allowing seamless auth options using email

Checklist

Please, make sure to comply with the checklist below before expecting review

• Code compiles correctly
• Created tests which fail without the change (if possible)
• All tests passing
• Extended the README / documentation, if necessary

[aorumbayev]

@drichar hey, let me know if there are any tweaks to address, ill merge latest from main and if you got some further comments can patch those up

[drichar]

Thank you so much for adding Magic Link support @aorumbayev! And I'm so sorry about the wait to get it reviewed.

I spun up the example in Storybook and it works flawlessly. 🚀

There are a few things to address in the code:

1. Since the API key is a required option, the ProviderDef union type should be updated to enforce this.
2. The provider.connect function exposed in the public API by the useWallet hook shouldn't accept an onDisconnect argument; it's used internally by the wallet clients' connect method. See my comment for a detailed explanation.

Besides that, there are a few other very minor change requests.

Overall it works great and I love the implementation. If you're busy (and don't mind), I'd be happy to make these changes myself to get this merged and released ASAP. Let me know what you'd prefer.

Thanks again for this, and for all of your contributions to the library! ❤️

[aorumbayev]

@drichar hey thank you for the review! Agree with all comments and I believe all should be addressed with last commits, also lmk if you are ok with tweaks in babel are ok, for some reason with latest magic sdks storybook started failing for me. Had to add extra plugin.

[drichar]

@aorumbayev Thank you for making these changes!

Yeah I'm fine with updating the Babel config for Storybook... I did update and remove some dependencies in https://github.com/TxnLab/use-wallet/releases/tag/v2.5.0 that might be the reason Storybook worked for you before and then didn't.

I've been thinking about the addition of the email argument to BaseClient's connect method, and wondering if it could potentially cause problems down the road. Perhaps it makes more sense to change it from from email?: string to arg?: any and doing a manual type check inside the individual provider(s)?

// something like:
if (typeof email !== 'string') {
  throw new Error('Magic Link provider requires an email (string) to connect')
}

Then if some future wallet provider needs to accept an argument to connect – say, an object – we won't be forced to either add a new optional argument or introduce a breaking change?

Let me know what you think. Besides that, everything else looks great!