ref(node): Add mechanism to errors captured via connect and koa integrations

[Lms24]

Adds mechanism following the trace origin naming scheme

closes #17261
ref: #17212

[cursor]

Bug: Span Origin Mismatch for Exception Capture

The mechanism type should align with SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN when a span wraps the captureException call. Connect spans use 'auto.http.otel.connect' as their origin, so the mechanism type should be 'auto.http.otel.connect' instead of 'auto.middleware.connect'.

 

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,120	-	9,109	+0%
GET With Sentry	1,296	14%	1,225	+6%
GET With Sentry (error only)	5,880	64%	5,775	+2%
POST Baseline	1,196	-	1,143	+5%
POST With Sentry	496	41%	451	+10%
POST With Sentry (error only)	1,061	89%	991	+7%
MYSQL Baseline	3,308	-	3,325	-1%
MYSQL With Sentry	429	13%	444	-3%
MYSQL With Sentry (error only)	2,706	82%	2,720	-1%

View base workflow run