Stabilize release-maven by removing race-prone assertion in testBatchUseCase3

[Copilot]

release-maven was failing due to a flaky async timing assumption in LocalConnectorInfoManagerTests.testBatchUseCase3. The test asserted zero results immediately after executeBatch, which intermittently fails when callbacks arrive before that assertion.

• Root cause

  • testBatchUseCase3 relied on fixed-delay timing (Thread.sleep(500)) and an immediate results.size() == 0 check in an asynchronous path.

• What changed

  • Reworked the test to assert deterministic end-state instead of transient pre-callback state.
  • Built the batch once and reused it for execution/size assertions.
  • Replaced fixed sleep with bounded completion polling (up to 3s) via isComplete.

• Behavioral impact

  • No production code changes.
  • Test now validates async batch completion semantics without race sensitivity.

final List<BatchTask> batchTasks = batch.build();
Subscription sub = facade.executeBatch(batchTasks, observer, options);

final long timeout = System.currentTimeMillis() + 3000;
while (!isComplete.get() && System.currentTimeMillis() < timeout) {
    Thread.sleep(100);
}

assertEquals(results.size(), batchTasks.size());
assertTrue(isComplete.get());
assertFalse(hasError.get());