feat(hono): Support middleware spans defined in app groups

[s1gr1d]

Patches app.route to also support middleware defined in Hono route groups.

The Node instrumentation still produces too many spans, this will be fixed in another PR - one test is skipped for now.

Closes#20449

[s1gr1d]

those are basically the tests like before, but split in two scenarios, with a different route prefix (/test-middleware and /test-subapp-middleware)

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 46f78a2. Configure here.}

[cursor]

Missing .filter() makes span assertion too broad

Medium Severity

The original test filtered spans with .filter(span => span.op === 'middleware.hono' && span.origin === 'auto.middleware.hono') before sorting. The refactored version drops the .filter() entirely, so middlewareSpans now contains all transaction spans, not just middleware spans. The subsequent toHaveLength(2) and description checks operate on the wrong set, making the test fragile and semantically incorrect.

^{Reviewed by Cursor Bugbot for commit 46f78a2. Configure here.}

[s1gr1d]

it's not filtered on purpose - makes the test too weak. We want to specifically check for all spans that are here