[legacy-framework] Next.js Fork Migration: Move query/mutation support into nextjs core

[flybayer]

What are the changes and their implications?

This is a huge step towards removing our custom compiler (and 1.0) by moving query/mutation support into nextjs core!

This implements the autogenerate route change discussed in #2010. This is a breaking change for anyone manually calling these routes.

-/api/auth/mutations/login
+/api/rpc/login
-/api/modules/users/queries/getUsers
+/api/rpc/getUsers

It also adds ability to version queries/mutations (also talked about in the above discussion)

FILE:    app/users/mutations/createUser.ts
API URL: /api/rpc/createUser

FILE:    app/users/mutations/v2/createUser.ts
API URL: /api/rpc/v2/createUser

---

• Query/mutation resolvers functioning
• Client build step step
• Global middleware
• Local middleware
• invokeWithMiddleware
• move auth to core
• Re-enable auth integration with RPC
• Move react-query stuff to core
• Move BlitzProvider to core
• Re-enable RQ integration with RPC
• Get blitz build working again
• Server logging
  • invokeWithMiddleware (DRY with rpcMiddleware)
  • rpcMiddleware
  • All API requests
• Fix invokeWithMiddleware to use resolver name
• Disable .warm feature
• Update getQueryKey
• NEXT_API_REQUEST -> BLITZ_API_REQUEST
• Update RPC specification docs
• Mark as breaking change release
• Test on Vercel

[flybayer]

PR reviews still welcome, even though this is merged!

[flybayer]

This change is available in https://github.com/blitz-js/blitz/releases/tag/v0.40.0-canary.0. Please test and report any issues!

[sam3d]

Amazing news!