test(e2e): Add cache origin link tests for cached components in pages - #24739

Add tests for cache_origin span links on use cache inside rendered pages: cached components and nested cached functions. The key claim beyond the route-handler case: links are per cache entry, so one render with several cached sections carries one link per section, each pointing at its own fill. Currently all in a "failed" state (test.fail()) as this is not yet implemented.

Both routes place the cached code in a dynamic hole (awaited searchParams). Entries served from the prerendered shell (Resume Data Cache) never reach the cache handlers and produce no spans — that path stays untestable until Next.js exposes RDC reads.

Legend
T1, T2       traces, one per request, in order
ck:X         cache.key digest of entry X
o--> put     span link (sentry.link.type: 'cache_origin'), target = the cache.put span

1. Sibling components: one link per section

app/cached-sibling-components/ — dynamic hole renders two cached sibling components
(props are part of the cache key => two entries)

T1 (fill)                              T2 (hit)
|- put ck:A (first)   <-------------------o get hit=true ck:A
|- put ck:B (second)  <-------------------o get hit=true ck:B

The two links must target two different fill spans — origin per section, not per page.

2. Nested caches with different lifetimes (production only)

app/nested-caches/ — cached component (expire: 2s) calls a nested cached fn (cacheLife('hours'));
sleep 3s between requests

T1 (fill)                              T2 (outer refill)
|- put ck:outer                        |- get hit=false ck:outer (expired)
|- put ck:inner  <------------------------o get hit=true  ck:inner
|- put ck:outer

The inner read happens inside the outer entry's isolated fill context and must still link back to T1.

Closes #24731
Linear: https://linear.app/getsentry/issue/JS-3804/cache-origin-link-tests-for-cached-components-in-pages