Add opt-in for dangerous linking

[jcdogo]

This is an updated pull request of #3557 since it was closed due to inactivity. We also have the same use case as the original author (@Gregoor).

@ThangHuuVu I've updated the pull request against the latest main branch so that it compiles, and I have also addressed the requested changes from the original pull request:

1. The allowDangerousEmailAccountLinking option was moved to OAuthConfig since it only applies to oauth providers.
2. Added documentation for the new option in docs/configuration/providers/oauth.md

☕️ Reasoning

By default account linking can only be done through an active session, to prevent account stealing from low-trust providers. Some next-auth users might trust their chosen providers enough to opt them into more lax account linking.

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

#3557
#5098
#5324
#4826
#4625
#4271

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
next-auth	⬜️ Ignored (Inspect)		Oct 20, 2022 at 5:43PM (UTC)

[balazsorban44]

The original PR does not seem to be closed, but due to inactivity, it might be in the future. I closed it and pointed to this PR, hopefully, the author will understand.

[dogomedia-github]

We have rebased the PR so that there is no longer a conflict with main branch. Hopefully we can get this one approved since account linking seems to have come up fairly frequently.

[ThangHuuVu]

Thanks for sending the PR 🙌 Could you run the linter on the PR again? Let's get this merged soon

[jcdogo]

Thanks for sending the PR 🙌 Could you run the linter on the PR again? Let's get this merged soon

I'm are running into some difficulties running the linter! Not sure how to fix it as this is our first time working with mono repo. We're getting this error when running the linter.

error  Parsing error: File '@next-auth/tsconfig/tsconfig.base.json' not found

Any ideas how to resolve this? (I suspect we just haven't set up something correctly)

EDIT: Never mind. Instead of trying to build this locally, we just looked at the Github Actions pull request output and noticed that it was calling the lint command anyways. After rebasing the code onto main branch again, we noticed that there was a linting error that was breaking the build (not due to our changes though). So in order to complete the linting, we added a fix for the linting error. There should no longer be any outstanding issues with lint.

[ThangHuuVu]

LGTM!