fix: Use correct recipeUserId when registering a WebAuthn credential

[coolbueb]

use the recipe user id from the payload and not from the session when registering a new credential

Summary of change

(A few sentences about this PR)

Related issues

• Link to issue1 here
• Link to issue1 here

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

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

Remaining TODOs for this PR

• Item1
• Item2

[cloudflare-workers-and-pages]

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

Latest commit:	1f43515
Status:	✅  Deploy successful!
Preview URL:	https://85ee348d.supertokens-node-b95.pages.dev

View logs

[porcellus]

Please add a changelog item