feat: Add edge compatibility for custom frameworks and Next.JS

[deepjyoti30Alt]

Summary of change

This PR adds fixes for various things that break when running this SDK with next.js on edge runtime.

Related issues

• Build error in next.js when using runtime = 'edge' #745

Test Plan

Testing with NextJS app router in edge runtime:

1. Setup the example app from the repo
2. Make all the server code use edge runtime by adding export const runtime = "edge"; to the top of the file.
3. Run npm run build or npm run dev (live server)
4. Both working without errors would indicate that the fix is working

Testing with NextJS pages router in edge runtime

1. Setup the example next app using pages
2. Make all the server code use edge runtime by adding export const runtime = "edge"; to the top of the file.
3. Run npm run build or npm run dev (live server)
4. Both working without errors would indicate that the fix is working

Test with express to confirm that inflate works with different compression methods:

1. Create a demo BE app with express
2. Inflate should work with br, gzip and deflate.
3. Create a JSON file with the body, call it body.json.
4. Create compressed versions using one of the following:

# For gzip
gzip -c body.json > body.gz

# For brotli
brotli -o body.br body.json

5. Run cURL request with the created body:

# For gzip
curl -v -i -X POST http://localhost:3001/auth/signin -H 'Content-Encoding: gzip' --data-binary @body.gz

# For brotli
curl -v -i -X POST http://localhost:3001/auth/signin -H 'Content-Encoding: br' --data-binary @body.br

6. Request should succeed successfully in order for the test to be successful.

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 failed.

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

[netlify]

❌ Deploy Preview for astounding-pegasus-21c111 failed.

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