Remove combination recipe/base

[rishabhpoddar]

Summary of change

Removing of combination recipe

Related issues

• Removing combination recipes supertokens-node#815

Test Plan

TODO

Checklist for important updates

• Changelog has been updated
• coreDriverInterfaceSupported.json file has been updated (if needed)
  • Along with the associated array in supertokens_python/constants.py
• frontendDriverInterfaceSupported.json file has been updated (if needed)
• Changes to the version if needed
  • In setup.py
  • In supertokens_python/constants.py
• Had installed and ran the pre-commit hook
• 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 supertokens_python/utils.py file to include that in the FRAMEWORKS variable
• If added a new recipe that has a User type with extra info, then be sure to change the User type in supertokens_python/types.py
• Make sure that syncio / asyncio functions are consistent.
• If access token structure has changed
  • Modified test in tests/sessions/test_access_token_version.py to account for any new claims that are optional or omitted by the core

Remaining TODOs for this PR

• Search for all places for thirdpartyemailpassword and thirdpartypasswordless and make sure they don't exist
• Test dashboard
• if input rid is tpep, or tpless, it should try and map to the the right breakup
• Add test for checking rid based on tpep and tpless
• remove rid from links generated by the sdk
• example app updates