fix(testing): Correct organization context for replay.id link test

[sentry]

This PR fixes the TestingLibraryElementError: Unable to find role="link" in fieldRenderers.spec.tsx.

The renders replay.id as a link when replay exists test was failing because the useReplayCount hook, which is used by ViewReplayLink, relies on useOrganization() to determine the organization slug for its API calls to /replay-count/.

When render() was called without explicitly passing the organization fixture, the OrganizationContext within the test environment was not correctly set. This caused useReplayCount to construct an API URL with a default/incorrect organization slug, which did not match the URL set up by MockApiClient.addMockResponse.

As a result, the mock API response was never triggered, the replay existence check failed, and ViewReplayLink rendered (missing) instead of the expected link, leading to the findByRole('link') assertion timing out.

The fix involves passing the organization fixture as an option to the render() call, ensuring that useOrganization() resolves the correct organization slug and the replay-count API call correctly hits the mock.

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 JEST-2332

[github-actions]

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.53%