Integrate Magic.Link within AWS Amplify ecosystem

### Is this related to a new or existing Amplify category?

auth

### Is this related to another service?

Cognito

### Describe the feature you'd like to request

Add [Magic.Link](https://magic.link/) as an OIDP.

### Describe the solution you'd like

Use Magic.Link as an IdP to work with AWS Amplify and relay on AWS powerful services to build on top and use Magic.Link functionality for web3 approaches on the app client.

### Describe alternatives you've considered

[Custom Lambda Authorization via AppSync](https://twitter.com/a_turl/status/1429276558045315075?s=20).

### Additional context

I [asked on Twitter to Nader Dabit](https://twitter.com/luisalrp/status/1429162510465347590) about if it would be possible to use magic link within AWS Amplify and I received a lot of feedback from Nader, Ricardo and Arek.

I've been thinking after reading answers on tuit the that Magic Link solves me a lot of things, specially in web3 universe but it breaks good practices in user authentication using 2/3 of knowledge, possession and inherence.

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request
- [ ] ⚠️ This feature might incur a breaking change

The request concerns the Amplify auth category, Cognito, and Magic.Link as an identity provider. Start by reviewing how the existing Amplify authentication integrations are structured; the issue does not name files or tests. Done would mean defining and implementing Magic.Link support as an IdP, with its compatibility and integration behavior established.

Written by the indexing model from the issue text.