Turbopack: disallow worker reuse after mid-evaluation protocol errors
Early error exits of pull_operation (protocol decode, info handler,
request decode, response encode, send failure) returned a possibly
mid-flight runtime to the pool as healthy: the JS worker is either still
running the aborted evaluation or waiting for a nested-request response
that will never arrive. Later tasks then hung on the wedged worker and
its in-flight state was retained. Mark the operation non-reusable on
every early exit so it is terminated through the existing worker
terminator.