[adamtheturtle]

A transient read failure during target_id setup restarted target creation, even after Vuforia had returned an ID. Retry processing polls and record reads against the existing target instead. Only an actual unsuccessful processing result triggers the existing bounded replacement behavior.

Attempt best-effort deletion after transient service/network read failures, exhausted target-visibility retries, or a processing timeout. Other setup errors propagate directly. During cleanup, suppress only the existing transient service/network exceptions, TargetStatusProcessingError, and UnknownTargetError so these expected failures preserve the setup error. Unexpected cleanup errors propagate with the setup error chained. The real adapter retains its cleanup of remaining targets before the next test.

Fixes #3767.

No new tests are added. The live-service failure paths retain coverage exclusions.

Validation:

• Existing target-name tests against the mock backends: 22 passed, 11 real-backend cases skipped.
• Pre-commit and pre-push hooks, including partition checks and all type checkers, passed.
• git diff --check passed.

Live-service and Docker validation remain with hosted CI.