would yall be open to a PR for including additional params from user input when kicking off an auth flow with a third party? Google for instance supports passing an

hd

param to restrict users to the provided domain in that param For Node, it looks like one would need to grab additional (allow listed?) params from the querystring and include them in authorisationUrl created here - https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/authorisationUrl.ts#L70