fix: Narrow exception handling in concurrent reset+query test

[phillipleblanc]

Changes

The testConcurrentResetAndQuery test had a catch-all Exception handler that silently swallowed all non-NPE exceptions. This meant:

• IllegalStateException (client incorrectly thinks it's closed during concurrent reset) would pass silently
• ExecutionException wrapping an NPE or ISE as its cause would also pass silently
• Any other unexpected exception type would be ignored

Fix

Replace the catch-all with an isExpectedTransportError() helper that:

1. Unwraps ExecutionException to inspect the real cause (since SpiceClient.query() wraps retried failures)
2. Allows only known transport errors: FlightRuntimeException (gRPC status errors), ConnectException/IOException (connection refused, broken pipe), and messages containing known transport keywords
3. Records as unexpected everything else — NPE, ISE, or any other exception that would indicate a bug in the reset/rebuild logic

Addresses review feedback from #40.

[Copilot]

Pull request overview

Updates ResetTest.testConcurrentResetAndQuery so that IllegalStateException is treated as an unexpected error (alongside NullPointerException) during concurrent reset() + query() operations, aligning the test behavior with its documentation and intent from PR #40.

Changes:

• Record IllegalStateException as an unexpected error in testConcurrentResetAndQuery (previously swallowed).
• Clarify inline comments describing which error types are expected vs unexpected.
• Update the assertion message to mention both NPE and IllegalStateException.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.