Drop RR requirement and simplify library a lot

[sergiodxa]

Change how the Authenticator and Strategy classes work to drop requirement of a Remix session storage at the authenticator level.

This simplifies many things in the library, since strategies can now define the cookie/session storage to store the intermediate state they may need (like OAuth state and PKCE values) or nothing if there's no reason to use one, then instead of Remix Auth handling how the user data is stored in the application session, that depends on the app.

Because of that the logout method was removed, all the sessionKey, etc. options were removed, the Strategy failure and success methods were removed and the successRedirect and failureRedirect methods were removed too.

The authenticate method will now return the user data returned by the strategy verify function, or it will throw. Here it depends on the strategy as it may only throw errors or in case of OAuth2 based strategies it may need to throw a redirect.

This also brings another important change, as Remix Auth itself doesn't depends on react-router or any @remix-run/* package, this means if a strategy doesn't depend on them this will work everywhere you can use Request and Response objects.

Only possible Remix/Rr requirement will be how to handle throw responses.

[stephen776]

Hey @sergiodxa - can we expect this to get merged? I am migrating to RR7 and remix-auth is one of the last hurdles. The peer dep on @remix-run/react is causing issues for me using pnpm

Happy to provide more info to assist.

[stephen776]

pnpm why react-router-dom gives me this:

and I am hitting runtime errors from things trying to import from react-router-dom