fix(webapp): reap OTLP workers on any exit, not just non-zero

A worker that exits cleanly (code 0) while holding a task previously left the
request hanging until the task timeout and the pool one worker short. Reap on any
exit; the double-reap guard makes this a no-op when error already reaped it.

Author: ericallam

apps/webapp/app/v3/otlpWorkerPool.server.ts

@@ -73,9 +73,9 @@ export class OtlpWorkerPool {
     });
 
     worker.on("exit", (code) => {
-      if (code !== 0) {
-        this.reap(worker, new Error(`otlp worker exited with code ${code}`));
-      }
+      // Any exit means this worker is gone, including a clean exit while it held a task; reap()
+      // no-ops if the worker was already removed (e.g. error fired first).
+      this.reap(worker, new Error(`otlp worker exited with code ${code}`));
     });
 
     this.workers.push(worker);