chore(docs): add client-side support for magic links using Next.js

[halvaradop]

☕️ Reasoning

This pull request adds code to the getting-started/authentication section for implementing magic links. It allows users to authenticate using magic links, providing a secure and user-friendly login method. The code demonstrates the client-side implementation in Next.js.

🧢 Checklist

• [x] Documentation
• [ ] Tests
• [x] Ready to be merged

🎫 Affected issues

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 15, 2024 2:28pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Sep 15, 2024 2:28pm

[vercel[bot]]

@halvaradop is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[halvaradop]

I have made changes similar to those in PR #11701. I added Object.fromEntries because the signIn function expects a value of type SignInOptions, which is an object. Additionally, I included the "use client" directive to indicate that the component works on the client side. We can discuss further if you have any questions or concerns about these changes.