fix(tests): Use findByRole for async options in opJsonPath.spec.tsx

[sentry]

This PR addresses JEST-22P5 by updating tests in static/app/views/alerts/rules/uptime/assertions/opJsonPath.spec.tsx.

The root cause was identified as a race condition where screen.getByRole('option', ...) was called immediately after userEvent.click() on a CompositeSelect trigger. The CompositeSelect component, which uses @sentry/scraps and React Aria, renders its options asynchronously. This meant that the options were not always present in the DOM when getByRole was executed, leading to a TestingLibraryElementError.

The fix involves replacing screen.getByRole('option', ...) with await screen.findByRole('option', ...) for the initial lookup of option elements after the dropdown trigger is clicked. findByRole includes built-in waiting and retrying logic, ensuring that the test waits for the asynchronous rendering of the options before attempting to query them, thus eliminating the flakiness.

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-22P5

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f93845b. Configure here.}

[github-actions]

📊 Type Coverage Diff

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