fix(operator): wait for inclusion on rollup-message injection

[devon-n]

Problem

Shields intermittently fail with the operator recording:

cannot be added because the mempool already contains a conflicting operation

Both inject_direct_message call sites (process_submission direct inbox, and the DalPointer submit after attestation) used octez-client -w none — fire-and-forget. The op enters the mempool but the call returns before it is baked, releasing advance_lock while the on-chain counter is still stale. octez-client derives each op's counter from on-chain state, so the next injection from the operator key reuses the same counter and L1 rejects it. The shield is marked failed (not retried); the next one self-recovers. ~3% of injections.

Fix

1. Wait for inclusion. Both sites now use -w 1, so each op is baked (counter advances) before advance_lock releases — the conflict can't occur.

2. Bounded wait. -w 1 blocks under the lock, so run_command_collect_output gets a 180s ceiling (capture to temp files, poll try_wait, kill on expiry). Without it, one never-confirmed op would hang the operator indefinitely.

3. Idempotent on post-injection error. octez-client prints the op hash the moment it injects, before waiting. If the wait then errors (timeout / RPC blip) the op already reached the node, so both call sites record it as SubmittedToL1 rather than Failed / re-injecting — otherwise the reconciler would inject a duplicate pointer op next tick.

Cost / assumptions

• Adds ~1 block (~8–16s) of latency per injection, held under advance_lock. Acceptable for the operator's throughput; removes the race deterministically.
• Correct under the operator's existing single-writer assumption (one process signs for the operator key). A second signer for the same key would reintroduce the counter race.
• (3) records an injected op as submitted without verifying inclusion; a genuinely dropped op is still caught by the caller's settlement timeout. On-chain inclusion verification is a possible future follow-up.

Test

cargo test -p tzel-services --bin tzel-operator → 33/33; build + clippy clean. New: pointer_inject_error_with_op_hash_is_recorded_not_retried, run_command_times_out_and_keeps_partial_output, and a -w 1 assertion on attested_dal_submission_sends_pointer_message.