feat: [Auth] Common AuthProvider & use* changes for middleware auth

[dac09]

Pairing with @dthyresson

• First step of supporting Auth using middleware. This PR is the smallest slice possible.
• Also removes the unused skipFetchCurrentUser, that was only used in nhost - a deprecated auth provider. This technically makes this change breaking, so we need to think it through!

To make use of this functionality, we will need:
1. A specialised middleware auth client
(naming TBC) - in your web/src/auth.ts, you will need to instantiate the create auth differently.

import {
  createDbAuthClient,
  createMiddlewareAuth, // 👈 not in this PR
} from '@redwoodjs/auth-dbauth-web'

const dbAuthClient = createDbAuthClient({
  middleware: true, // 👈 not in this PR
})

export const { AuthProvider, useAuth } = createMiddlewareAuth(dbAuthClient)

2. The middleware to perform auth

export const registerMiddleware = () => {
  console.log('Registering middleware')
  const dbAuthMiddleware = createDbAuthMiddleware({
    cookieName,
  })
  return [dbAuthMiddleware]
}

4. Updated dbAuth handler for dbAuth

Checklist

• Ensure backwards compatibility with non-SSR auth
• Should we undo the changes to skipFetchCurrentUser

[dac09]

@dthyresson what do you think of looking at the outstanding checklist here? I think it would be helpful to have the person not writing the code do the validation, right?

[dthyresson]

@dthyresson what do you think of looking at the outstanding checklist here? I think it would be helpful to have the person not writing the code do the validation, right?

For

Should we undo the changes to skipFetchCurrentUser

As I understand it, skipFetchCurrentUser was introduced as nHost's auth required it -- but nHost 1) no longer exists as a service and 2) no longer supported as an auth provider. Unless we can think of a reason to keep it (how it would be used moving forward) it seems ok to remove to and listed as a potential breaking change.

[dthyresson]

Confirmed that with classic GraphQL and dbAuth, cookie dbAuth behaves as expected:

• sign up
• login
• permissions respected
• cookie set