Upgrade to Remix Auth v4 and use Arctic's OAuth2Client

[sergiodxa]

This PR does two things

1. It upgrade the strategy to work with Remix Auth v4, the strategy uses @mjackson/headers to work with cookies and accepts an optional cookie configuration that fallbacks to oauth2, this cookie is used as the name of the cookie the strategy will use to keep the state and code verifier.

The cookie can also be an object to customize path, maxAge, secure, httpOnly, etc.

2. It change how it works internally to use the new Arctic's OAuth2Client, this way the strategy just instantiate the client and coordinate with the request->response flow how to read from the URL and cookies and how to direct, but the actual logic for OAuth2 is on the client.

This has a side-effect that now an identity provider that doesn't really follow the spec will not work, for those is better to create a custom strategy.