OpenTelemetry Tracing is poluted with some extra spans from middlewares

Link to the code that reproduces this issue

https://github.com/pksorensen/nextjs-repro-otel

To Reproduce

configure som otel endpoint and replace .env
Start npm run dev
monitor traces

Current vs. Expected behavior

It is emiting this wierd trace with next.bubble | true which seems related to old bug https://github.com/vercel/next.js/issues/55752 where i dont fully get what is going on at

The expected trace is there also which has all the childs,

so either that first one /da/ should be a child of /[locale] or not there at all ?

I think its related to also that middleware does not run with the same traceid that the request is doing.

I added

function withTraceParent(res: NextResponse) {
    const spanContext = trace.getActiveSpan()?.spanContext();
    if (spanContext)
        res.cookies.set("traceparent", `00-${spanContext.traceId}-${spanContext.spanId}-0${spanContext.traceFlags}`);
    return res;
};

to the middleware and can inspect that the traceparent set in cookie from within the middleware is totally different from those in the above request (either of the two base requests)

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise N
  Available memory (MB): 32687
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.65 // Latest available version is detected (15.0.0-canary.65).
  eslint-config-next: N/A
  react: 19.0.0-rc-6f23540c7d-20240528
  react-dom: 19.0.0-rc-6f23540c7d-20240528
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Internationalization (i18n), Middleware

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Other (Deployed)

Additional context

No response

vercel / next.js