feat(nextjs): Trace errors in page component SSR

[lforst]

This will attach errors happening while serverside rendering page components to the corresponding transaction.

Resolves #9152

Note: Ideally we would have a span for rendering the page and attach the error there but this would be messy to do with our current implementation. The reason is that we cannot directly grab the request transaction from within the render function because it doesn't live in the current async context. We would have to pass references or keys around and clean them up after a response has been sent so the transactions can be GCd. The mess would originate from the fact that we create spans and transactions differently depending on whether we're in a lambda environment.

We will do span creation in a follow-up PR.