fix(nuxt): Remove redundant Nitro 3 route-name plugin

On Nitro 3, `@sentry/server-utils`' `nitroIntegration` (auto-injected via
`@sentry/node`'s defaults) already sets the parametrized route name and
`url.path.parameter.*` attributes for API routes, and `route-detector.server`
handles SSR page routes. Nuxt's `update-route-name.server` set the same
attributes on the same span — redundant work with no extra telemetry — so it is
removed for Nitro 3. Legacy Nitro (v2), which has no native tracing channels,
keeps its own plugin, and the shared `updateRouteBeforeResponse` hook stays for
the legacy and Cloudflare paths.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: mydea

packages/nuxt/src/module.ts

@@ -112,7 +112,10 @@ export default defineNuxtModule<ModuleOptions>({
 
       if (isNitroV3) {
         addServerPlugin(moduleDirResolver.resolve('./runtime/plugins/handler.server'));
-        addServerPlugin(moduleDirResolver.resolve('./runtime/plugins/update-route-name.server'));
+        // On Nitro 3, the parametrized route name and `url.path.parameter.*` attributes are set by
+        // `@sentry/server-utils`' `nitroIntegration` (auto-injected via `@sentry/node` defaults) for
+        // API routes, and by `route-detector.server` for SSR page routes, so no Nuxt route-name
+        // plugin is needed. Legacy Nitro (v2) has no such channels and keeps its own.
       } else {
         addServerPlugin(moduleDirResolver.resolve('./runtime/plugins/handler-legacy.server'));
         addServerPlugin(moduleDirResolver.resolve('./runtime/plugins/update-route-name-legacy.server'));