`response` context not set on Node SDKs

[shruthilayaj]

Description

Related to: getsentry/sentry#81418
User is not able to search/aggregate on http status code. This is because discover reads this value from the response context and it seems like that's not being set on their events (nextjs SDK, same case on our docs project).

Example event from our docs project https://sentry.sentry.io/api/0/projects/sentry/docs/events/df769fee6ff14658be47ab545dc717bc/json/
Or docs project is on sentry.javascript.nextjs version 8.36.0

[mydea]

It seems we are generally not setting this context so far, we'll adjust this accordingly!

[mydea]

Side note: Just to bring this up here, we should probably look to also look at the transaction (root span) attributes (today in trace context data) there too, as at some point we will not send contexts like this anymore (OTEL alignment, ...). The semantic attribute for this is http.response.http_status I believe (cc @AbhiPrasad )

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #14634, which was included in the 8.44.0 release.