feat: replace psl deprecation warning by using tldts

[deepjyoti30-st]

Summary of change

This PR fixes a deprecation warning regarding the punycode module which was not a direct dependency but a dependency of psl module. The psl module has the fix merged [reference PR] but has not had a release since the last 2 years (no release after the fix was merged).

This PR uses an alternative package tldts for replacing the functionality provided by the psl package.

Related issues

• DeprecationWarning: The punycode module is deprecated. supertokens-core#1049

Test Plan

• All utils.test.js 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

[cloudflare-workers-and-pages]

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

Latest commit:	d1c5938
Status:	✅  Deploy successful!
Preview URL:	https://099d9994.supertokens-node-b95.pages.dev

View logs