feat!: update viewer dev middleware to be compatible with h3@0.8

[DamianGlowala]

PR addresses a breaking change introduced in h3@0.8, which yields a warning on the latest Nuxt edge:

[n4an]

But what to do with that

Implicit event handler conversion is deprecated. Use eventHandler() or fromNodeMiddleware() to define event handlers.
Handler: function csrf (req, res, next) {

[danielroe]

That is likely another middleware injected by a different module. You will need to find out which module is adding the 'csrf' middleware and raise an issue there.

[valh1996]

Hi @danielroe

I have the same issue :

 WARN  [h3] Implicit event handler conversion is deprecated. Use eventHandler() or fromNodeMiddleware() to define event handlers.                                                          12:05:12
     Route: /_tailwind 
     Handler: (req, res) => viewerDevMiddleware(new H3Event(req, res))

Here is my config:

- Operating System: Darwin
- Node Version:     v20.8.0
- Nuxt Version:     2.17.2-28271541.6132947
- CLI Version:      3.8.4
- Nitro Version:    2.6.3
- Package Manager:  npm@10.1.0
- Builder:          webpack
- User Config:      bridge, head, css, plugins, components, buildModules, modules, build, axios, runtimeConfig, auth, toast, i18n, router, serverHandlers, devServerHandlers, devServer, typescript, nitro
- Runtime Modules:  @nuxtjs/axios@5.13.6, @nuxtjs/auth-next@5.0.0-1642083611.1785b0f, @nuxtjs/toast@3.3.1, @nuxtjs/i18n@7.3.1, portal-vue/nuxt, @nuxtjs/tailwindcss@6.8.0
- Build Modules:    (), @nuxt/postcss8@1.1.3, @nuxt/bridge@3.0.0-rc.1-28271265.8fa71e1

Is it normal?