fix(retrieval): surface silent IPNI timeouts in logs

[SgtPooki]

What changed

Two adjacent observability bugs left IPNI failures invisible whenever the outer pg-boss retrieval-job timeout fired:

1. `IpniVerificationService.verify` check-order. Catch checked `signal?.aborted` before `verificationSignal.aborted`. On a race where both signals had asserted by the time the catch handler ran, `signal.throwIfAborted()` re-threw before the `ipni_verification_timed_out` log could fire. The inner-timeout log path was effectively dead code whenever outer ≤ inner. Inner check now runs first so the log fires whenever the inner timer aborted.

2. `RetrievalService.verifyIpniForRetrieval` silent abort. The catch's signal-aborted branch returned a silent `failure.timedout` with no event log. Added `retrieval_ipni_verification_timed_out` so the retrieval-side caller records the abort.

Implements option C from #524. Stacks on #538.

Files

• `apps/backend/src/ipni/ipni-verification.service.ts` — swap catch order so inner-timeout check wins same-tick races.
• `apps/backend/src/retrieval/retrieval.service.ts` — add `retrieval_ipni_verification_timed_out` log in the abort branch.
• `apps/backend/src/ipni/ipni-verification.service.spec.ts` — new test verifying `ipni_verification_timed_out` fires when both signals abort in the same tick.
• `apps/backend/src/retrieval/retrieval.service.spec.ts` — new test verifying `retrieval_ipni_verification_timed_out` fires when outer signal aborts and IPNI verify throws.

How to verify

```
pnpm --filter dealbot-backend typecheck
pnpm --filter dealbot-backend lint
pnpm --filter dealbot-backend test
```

After deploy, staging logs should show `ipni_verification_timed_out` events 1:1 with `retrievalStatus=failure.timedout` deltas for SPs without IPNI advertisements (currently SP 5 Mongo2Stor, SP 17 superusey-calib in staging).

Notes

Base branch is `feat/retrieval-parallel-transport-counter` (#538). Re-target to `main` after that PR merges.

[Copilot]

Pull request overview

Two small observability fixes for IPNI verification timeouts in the retrieval check. The first reorders the catch handler in IpniVerificationService.verify so the inner-timeout log fires even when the outer job signal aborts in the same tick. The second adds a retrieval_ipni_verification_timed_out warn log in RetrievalService.verifyIpniForRetrieval's outer-abort branch, replacing a silent failure.timedout return. Both changes have accompanying unit tests.

Changes:

• Swap catch-order in ipni-verification.service.ts so timeoutSignal.aborted is checked before the external signal?.aborted rethrow.
• Emit retrieval_ipni_verification_timed_out log in retrieval.service.ts when the outer signal aborts during IPNI verify.
• Add unit tests for both code paths.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
apps/backend/src/ipni/ipni-verification.service.ts	Reorder catch checks so inner-timeout log wins same-tick races.
apps/backend/src/ipni/ipni-verification.service.spec.ts	Test that ipni_verification_timed_out fires when both signals abort in the same tick.
apps/backend/src/retrieval/retrieval.service.ts	Add structured warn log on outer-signal abort in verifyIpniForRetrieval.
apps/backend/src/retrieval/retrieval.service.spec.ts	Test that retrieval_ipni_verification_timed_out fires when outer signal aborts and IPNI verify throws.