fix: Cache getJSONBody and getFormData response (Fixes #746)

[anku255]

Summary of change

In many frameworks, calling req.body or req.formData is limited to a single use due to their nature as readable streams. Our framework classes have getJSONBody and getFormData functions, designed to invoke the appropriate method on the req object.

Calling these functions multiple times can lead to issues, as observed in #746. For instance, the getJSONBody was mistakenly called twice in the passwordReset API implementation. Although combining these calls into one resolved the specific case in #746, it does not prevent users from inadvertently triggering the same error by calling getJSONBody multiple times.

To address this, we now cache the response of req.body or req.formData directly in the recipe implementation.

Related issues

• https://github.com/supertokens/supertokens-node/issues/746

Test Plan

Tests were added to ensure that getJSONFromRequestBody and getFormDataFromRequestBody are invoked only once, regardless of the number of calls to getJSONData or getFormData. If any framework class overrides the implementation of getJSONData or getFormData from the BaseRequest class, these tests would fail.

Documentation 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)
• [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.

[netlify[bot]]

✅ Deploy Preview for precious-marshmallow-968a81 canceled.

Name	Link
🔨 Latest commit	49bf2653accdca06a807328f3f76d87e9ae64f4f
🔍 Latest deploy log	https://app.netlify.com/sites/precious-marshmallow-968a81/deploys/655c94908a76290008824413

[netlify[bot]]

✅ Deploy Preview for astounding-pegasus-21c111 canceled.

Name	Link
🔨 Latest commit	49bf2653accdca06a807328f3f76d87e9ae64f4f
🔍 Latest deploy log	https://app.netlify.com/sites/astounding-pegasus-21c111/deploys/655c949056d4ef0008fea681

[rishabhpoddar]

Also, the AWS lambda PR check is failing.