chore(#892): rename middleware to avoid conflicts

[zoey-kaiser]

🔗 Linked issue

Closes #892

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR renames our internal middleware from auth to sidebase-auth. This is a quality of life change, as many people like to write their own authentication middleware on top of ours, or want to replace it.

A logical name for this middleware is often auth, however this results in nuxt warning messages, as it conlides with our built-in middleware. As the middleware name of our module does not have a big impact on our development or the usage inside the app, I renamed the middleware to sidebase-auth to free up the auth middleware name.

This PR does contain a breaking change, as when you want to add the middleware to a page, you need to change the following:

definePageMeta({
-  middleware: 'auth'
+  middleware: 'sidebase-auth'
})

This only impacts the case where you globally disable the middleware and only want to enable it on a certain page. However, configuring the middleware via the page meta remains unchanged:

definePageMeta({
  auth: {
    unauthenticatedOnly: false,
    navigateUnauthenticatedTo: '/auth/signin'
  }
})

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@sidebase/nuxt-auth@957

commit: 15f3cad