fix: resolve result_future on inference error instead of tearing down the model

[AmirF194]

Root cause

QueueWorker.queue_worker_llm and the identical loop repeated in every other
worker (vlm, whisper, qwen3_asr, kokoro, qwen3_tts, emb, rr)
broke out of its while True loop on an inference error before ever calling
packet.result_future.set_result(...). Non-streaming callers such as
WorkerRegistry.generate() await that future, so a failed generation hung
the caller forever. The same branch also fired an unconditional
registry.register_unload(model_name); that unload's pipeline destructor can
touch a corrupted device context after certain errors and abort the whole
process, taking every other loaded model down with it. This matches the issue
exactly for the LLM worker; I confirmed by reading each of the other seven
worker functions that they share the identical structural bug (grep/ast
enumeration in src/server/worker_registry.py), not only the ones named in
the issue as "likely" affected.

emb and rr trigger on a different condition (not completed_packet.response,
since InferWorker.infer_emb/infer_rerank already tag a raised exception as
a truthy "Error: ..." string, so that branch is actually reached only when
the pipeline returns no data with no exception), but the same break-before-resolve
bug is there too.

Fix

Each worker now reports the failure through result_future.set_exception(...)
and continues its loop instead of breaking, so a failed request surfaces as
an error to its caller and the worker/model stay alive to serve the next
request, per the issue's suggested design.

Verification

• New tests/unit/test_worker_registry_error_handling.py drives the real
  (unmocked) queue_worker_* loop for all 8 workers with a failing request
  followed by a healthy one. Confirmed fails on unmodified main (each
  test times out waiting on result_future, matching the reported hang) and
  passes on this branch, in a clean python:3.12-slim container.
• Full uv run pytest -W ignore tests/unit: 119 passed (was 111), no
  regressions.
• coverage run --source=src.server.worker_registry: every line this diff
  changes is exercised by the new tests.
• Not checked: the reported SIGABRT itself, since that needs a real Intel
  GPU/OpenCL context corrupted by a genuine device error, which this session
  doesn't have. This PR removes the register_unload call on the error path
  entirely (the mechanism the issue names as the crash trigger), but I can't
  reproduce the abort to confirm the crash is gone, only that the code no
  longer calls the destructor on that path.

Fixes #153

[SearchSavior]

@AmirF194 Thanks for the PR!

RE:

Not checked: the reported SIGABRT itself, since that needs a real Intel
GPU/OpenCL context corrupted by a genuine device error, which this session
doesn't have.

Does this mean the proposed fix has not been tested on hardware?

[AmirF194]

Correct, not on real Intel GPU/OpenCL hardware, this session doesn't have one. What's verified: the hung future (the caller never gets a response) and that all 8 worker functions share the same break-before-resolve pattern, both confirmed by running the workers directly. The SIGABRT itself I can't reproduce without a genuine device error on real hardware, so the fix removes the crash-triggering call (register_unload tearing down the model on the error path) rather than catching the abort, which should hold regardless, but I can't claim to have watched it not crash on your hardware. Happy to have someone with an Intel GPU confirm before merge if that matters here.