chore!: Bump github.com/golang-jwt/jwt to v5

[constantoine]

Summary of change

• Bumped github.com/golang-jtw/jwt version from v4 to v5.

• Bumped github.com/MicahParks/keyfunc version from v1 to v2.

• This PR is breaking because of a change in *keyfunc.JWKS.

Related issues

• jwt parser not accounting for clock skew #362

Test Plan

I ran the existing tests to ensure there was no regression.

Checklist for important updates

• Changelog has been updated
• coreDriverInterfaceSupported.json file has been updated (if needed)
  • Along with the associated array in supertokens/constants.go
• frontendDriverInterfaceSupported.json file has been updated (if needed)
• Changes to the version if needed
• In supertokens/constants.go > version variable
• Had installed and ran the pre-commit hook
• If new thirdparty provider is added,
  • update switch statement in recipe/thirdparty/providers/config_utils.go 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 access token structure has changed
  • Modified test in session/accessTokenVersions_test.go to account for any new claims that are optional or omitted by the core

Left to do

• Create new unreleased branch
• Reflect about whether the breaking change is worth or not

[rishabhpoddar]

Thanks for this PR @constantoine. We have also added you to the core's repo readme.