feat(nextjs): Support node runtime on proxy files

[chargome]

Next 16 was released

With that proxy files run per default on nodejs.

This PR

• Updates the tests to run on next 16 (non-beta)
• Adds support for handling middleware transactions in the node part of the sdk

closes #18006
closes #18005
closes #18008

[logaretm]

Tests are timing out and don't seem to be hitting the server, is that expected?

[chargome]

No, something has changed in between beta and stable release, the proxy invocations are not sending any spans atm – currently investigating

[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	8,797	-	9,475	-7%
GET With Sentry	1,366	16%	1,349	+1%
GET With Sentry (error only)	6,071	69%	6,020	+1%
POST Baseline	1,180	-	1,189	-1%
POST With Sentry	506	43%	513	-1%
POST With Sentry (error only)	1,043	88%	1,072	-3%
MYSQL Baseline	3,285	-	3,320	-1%
MYSQL With Sentry	478	15%	431	+11%
MYSQL With Sentry (error only)	2,686	82%	2,688	-0%

View base workflow run

[andreiborza]

Would be nice to also have a middleware test that still runs on edge.

[cursor]

Bug: Test Code Cluttered by Debugging Statements

A console.log debugging statement was accidentally committed to the test code. It outputs detailed transaction event information, which clutters test console output.

 

[chargome]

created vercel/next.js#85261 to track the error behaviour in proxy files