fix: Add changes to support unknown type in formField values

[deepjyoti30-st]

Summary of change

Makes the internal type of formField values to be unknown instead of string. Also adds test for signup/password reset API's when they get non string type of values for email/password.

PS: Updated the bad input error for email/password being invalid to keep it same as Go/Python SDK's

NOTE: Did not update Changelog as that was updated in the previous PR to indicate that any support is added for formField values.

Test Plan

• signup, signin and passwordReset tests for emailpassword should pass.

Documentation changes

(If relevant, please create a PR in our docs repo, or create a checklist here highlighting the necessary changes)

Checklist for important updates

• [x] Changelog has been updated
• [ ] coreDriverInterfaceSupported.json file has been updated (if needed)
  • Along with the associated array in lib/ts/version.ts
• [ ] frontendDriverInterfaceSupported.json file has been updated (if needed)
• [ ] 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.
• [ ] If added a new entry point, then make sure that it is importable by adding it to the exports in package.json

Remaining TO-DO's

• [x] Run build-pretty once the base branch issues are fixed

[cloudflare-workers-and-pages[bot]]

Deploying supertokens-node-pr-check-for-edge-function-compat with    Cloudflare Pages

Latest commit:	2cbab88
Status:	✅  Deploy successful!
Preview URL:	https://98850b14.supertokens-node-b95.pages.dev

View logs