Vercel source maps for server errors pointing to Sentry code not original code

### Is there an existing issue for this?

- [X] I have checked for existing issues [https://github.com/getsentry/sentry-javascript/issues]()
- [X] I have reviewed the documentation [https://docs.sentry.io/]()
- [X] I am using the latest SDK release [https://github.com/getsentry/sentry-javascript/releases]()

### How do you use Sentry?

Sentry Saas ([sentry.io]())

### Which SDK are you using?

@sentry/nestjs

### SDK Version

10.22.0

### Framework Version

Next

### Link to Sentry event

*No response*

### Reproduction Example/SDK Setup

*No response*

### Steps to Reproduce

Issue reported here: [https://community.vercel.com/t/server-side-stack-traces-for-next-js-typescript-on-vercel/26617]()
More information and a reproduction app are available in the link above.
Obs: if using the repro above, update org/project in next config before building.

### Expected Result

Events from Vercel are sourcemapped and the stack trace points to the correct source file.
Example event: [https://dev-curumas.sentry.io/share/issue/daaf14089cec4f558748c56da8aa75c1/]()

### Actual Result

Source map points to \`/sentry-wrapped-module instead.
Example event: [https://dev-curumas.sentry.io/share/issue/c6bcc2dc076149cab36d7fec2efdb711/]()

It is unclear if this is related to how Sentry wraps the code or how Vercel generates source maps. Result is the same when disabling the experimental server source maps.

### Additional Context

Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it.