GOL-420: capture correlated WASI HTTP lifecycle traces

[noise64]

What changed

• add fixed-size, lock-free P2/P3 outgoing HTTP lifecycle journals to the runtime test host
• correlate each test-host request with normal and abort-server arrival, body, response-head, drop, and transport-I/O events
• attach decoded client/server journals and existing Wasmtime HTTP warnings only when an invocation fails
• preserve stock and Golem Wasmtime default dispatch semantics, including P2 body-completion ownership

Why

GOL-420 tracks intermittent concurrent IncompleteMessage, HttpProtocolError, malformed-root-task, and pre-server-arrival abort failures that pass unchanged on rerun. This draft is the diagnostic tranche: it captures the first broken lifecycle boundary without retries, serialization, longer timeouts, or production/localhost branches. It does not claim a behavioral fix yet.

Validation

• tools/dev-test.sh p2 fast-start runtime xhr_post_with_json_body
• tools/dev-test.sh p2 fast-start runtime fetch_abort_releases_request
• tools/dev-test.sh p2 fast-start runtime p2_body_method_drops_unused_completion
• tools/dev-test.sh p3 standard runtime fetch_with_referrer
• tools/dev-test.sh p3 standard runtime http_lifecycle (6 focused journal/correlation tests)
• cargo clippy --test runtime -- -D warnings
• cargo fmt -- --check

Next evidence gate

Run the concurrent P2 groups 2 and 4 and P3 group 2 matrices repeatedly, stop at the first traced failure, and select a behavioral owner only from the correlated terminal events. GOL-405 remains separate unless those traces prove the same owner.