feat: always validate emails in pwreset and try linking

[porcellus]

Summary of change

Modified password reset API impl to always try to verify the email and try linking by account info

Related issues

Test Plan

• Account linking related tests:
  • Resetting the password of an existing EP w/ no related primary user and AL enabled makes the user primary
  • Resetting the password of an existing EP w/ related non-primary TP user and AL enabled makes the user primary and links the two accounts
  • Resetting the password of a primary user marks the right email as verified
  • if there are multiple email password recipe users
  • if there are multiple login methods (with different email addresses)
  • if there are multiple login methods (with different email addresses) and linking is disabled
  • if there is a verified TP login method and unverified EP with the same email
• Non-account linking tests:
  • It works without email verification (and doesn't mark it as verified)
  • It works with email verification and marks the email as verified

Documentation changes

• [ ] Update the password reset flow references in the automatic linking docs

Checklist for important updates

• [x] Changelog has been updated
• [x] coreDriverInterfaceSupported.json file has been updated (if needed)
  • Along with the associated array in lib/ts/version.ts
• [x] frontendDriverInterfaceSupported.json file has been updated (if needed)
• [x] Changes to the version if needed
  • In package.json
  • In package-lock.json
  • In lib/ts/version.ts
• [x] Had run npm run build-pretty
• [x] Had installed and ran the pre-commit hook
• [ ] If new thirdparty provider is added,
  • [ ] update switch statement in recipe/thirdparty/providers/configUtils.ts file, createProvider function.
  • [ ] add an icon on the user management dashboard.
• [x] Issue this PR against the latest non released version branch.
  • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
  • If no such branch exists, then create one from the latest released branch.
• [ ] If have added a new web framework, update the add-ts-no-check.js file to include that
• [ ] If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}).
• [ ] If added a new recipe, then make sure to expose it inside the recipe folder present in the root of this repo. We also need to expose its types.