[orchestrator]: investigate `native_tls_driver` stuck behavior

### Problem:
When run as part of the orchestrator, the `native_tls` client driver process gets stuck and never terminates. This results in the orchestrator never finishing and also hanging forever. Only the `native_tls` driver exhibited this behavior.

### Observed behavior
- the behavior would occur when running the incast scenario with 5+ server
- the issue became more reproducible when using multiple servers

Start by reproducing the incast scenario with 5 or more servers and the native_tls client driver, then trace where the driver and orchestrator wait for termination. The issue is done when the native_tls driver exits reliably and the orchestrator completes under the multi-server case.

Written by the indexing model from the issue text.