Fix ErrorBoundary retry test: resolve re-throw race condition

[Copilot]

The "provides try again button that resets error state" test was failing because clicking "Try Again" before providing new children caused a re-throw cycle: the boundary reset to hasError: false, synchronously re-rendered the still-throwing children, and getDerivedStateFromError fired again before rerender could supply the non-throwing replacement.

Fix

Swap the order of rerender and fireEvent.click in the test to reflect the correct lifecycle: parent provides updated children first, then the user retries.

- fireEvent.click(screen.getByText('Try Again'));
  rerender(
    <ErrorBoundary>
      <ThrowError shouldThrow={false} />
    </ErrorBoundary>
  );
+ fireEvent.click(screen.getByText('Try Again'));

When "Try Again" is clicked, the boundary resets state and renders the already-updated (non-throwing) children, completing the retry successfully.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.