feat: remove fastify with type implementation

[deepjyoti30-st]

Summary of change

This PR replicates fastify types that are used in the SDK to avoid type mismatches through different versions of fastify. This was as reported by an user on discord (and later on reproduced locally by using the sdk with fastify 5.x)

This also updates the fastify example to test with the newly added changes. The fastify version was bumped to 5.x and as a result some other dependencies (like typescript, formbody, cors) had to be updated.

Another thing to note is, react-scripts is a dependency of the fastify example's frontend code and it had a TS version related conflict with latest fastify requirements so I moved it to be a dependency of frontend directory and added a preinstall script to install this dependency when npm i is run.

Related issues

Test Plan

Fastify example tests 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

• 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
• Had run npm run build-pretty
• 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.
• 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

[netlify]

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

Name	Link
🔨 Latest commit	e95edd3
🔍 Latest deploy log	https://app.netlify.com/sites/precious-marshmallow-968a81/deploys/66fb8f7ae32a2800084dba82

[netlify]

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

Name	Link
🔨 Latest commit	e95edd3
🔍 Latest deploy log	https://app.netlify.com/sites/astounding-pegasus-21c111/deploys/66fb8f7ada6b9f00088c9fe9

[cloudflare-workers-and-pages]

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

Latest commit:	f7e4d52
Status:	✅  Deploy successful!
Preview URL:	https://cee47ccb.supertokens-node-b95.pages.dev

View logs