test: add a test that checks how we handle nullable access token payload props

Summary of change

add a test that checks how we handle nullable access token payload props

Test only change

Test only change

[ ] 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
[x] Had run npm run build-pretty
[x] Had installed and ran the pre-commit hook
[x] 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.
[x] 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.
[x] If have added a new web framework, update the add-ts-no-check.js file to include that
[x] If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}).
[x] 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.