Should we move email input normalising to the backend SDK instead of the core?

[rishabhpoddar]

• We make all email lower case, this can have an issue with users who use emails from providers that are case sensitive: https://twitter.com/gedamore/status/1408176756297670660
• Moving the normalisation to the backend SDK (in the API implementation), would allow users to bypass this normalising step if needed.
• In general, should we not normalise any "pure" user facing input in the core? By pure user facing, we mean that things like email / passwords etc.. that are "Created" by the user - as opposed to things like paginationTokens, access tokens, user IDs.. that are created by the core itself.
• See https://github.com/supertokens/supertokens-core/wiki/Recipe-development-guideline-for-the-backend-and-frontend-recipes -> section 1) -> point 12)

[rishabhpoddar]

We should do it in the backend SDK as per: https://github.com/supertokens/supertokens-core/wiki/Recipe-development-guideline-for-the-backend-and-frontend-recipes Section 3b4