fix(structuredEventData): Move Wrapper component to module scope

[sentry]

This PR addresses a static-component-definitions convention violation in static/app/components/structuredEventData/recursiveStructuredData.tsx.

The Wrapper component was previously defined as a nested function within the RecursiveStructuredData component's render body. This causes React to treat it as a new component type on every render, leading to unnecessary unmounting/remounting of its subtree, state resets, and blocking of React Compiler optimizations.

The fix involves moving the Wrapper component to module scope and passing formattedObjectKey as an explicit prop, rather than relying on closure over a render-time value. This ensures Wrapper has a stable identity across renders, resolving the convention violation.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Fixes CODING-CONVENTIONS-35R

_{Comment @sentry <feedback> on this PR to have Autofix iterate on the changes.}

[ryan953]

replaced by #120038