fix(e2e): Restore strict HTTP spans assertion

Revert the relaxation of the HTTP spans check from >= 1 back to exactly 2.
The other fixes (simulator warm-up, wait_for_boot, clearState, per-flow
retries) address the actual flakiness; weakening this assertion would
permanently hide regressions where one tracing layer stops producing spans.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: antonis

samples/react-native/e2e/tests/captureSpaceflightNewsScreenTransaction/captureSpaceflightNewsScreenTransaction.test.ts

@@ -131,18 +131,16 @@ describe('Capture Spaceflight News Screen Transaction', () => {
     );
   });
 
-  it('contains articles requests spans', () => {
-    // This test ensures we are tracing requests on different layers
+  it('contains exactly two articles requests spans', () => {
+    // This test ensures we are tracing requests multiple times on different layers
     // fetch > xhr > native
-    // On slow CI VMs, not all HTTP span layers may complete within the transaction,
-    // so we check for at least one HTTP span.
 
     const item = getFirstNewsEventItem();
     const spans = item?.[1].spans;
 
     const httpSpans = spans?.filter(
       span => span.data?.['sentry.op'] === 'http.client',
     );
-    expect(httpSpans?.length ?? 0).toBeGreaterThanOrEqual(1);
+    expect(httpSpans).toHaveLength(2);
   });
 });