test(e2e): pin GET codec-streaming body/header parity vs legacy duplex (backlog#1183) (#4745)

backlog#1183 tracks flipping the default GET data path from the legacy
tokio::io::duplex double-copy to the zero-duplex codec-streaming fast path.
That flip is gated behind RUSTFS_GET_CODEC_STREAMING_BODY_COMPAT_CONFIRMED /
..._HEADER_COMPAT_CONFIRMED, which need empirical evidence the two paths are
byte- and header-identical.

Add an e2e regression net that runs the same object matrix twice against the
same on-disk EC shards, changing only the codec-streaming env gates: phase A
(default) takes the legacy duplex path, phase B (gates opened) takes codec
streaming. It asserts byte-for-byte (sha256) and header-for-header equality
across inline / small / multi-block (1.5M/3M/5M+) / multipart objects, plus a
ranged GET (which falls back to legacy by gate design). Path confirmation is
not assumed: the legacy path logs "Created duplex pipe ..." per full GET, so
the test counts that marker per phase and asserts the codec phase created zero
duplex pipes, proving the fast path actually ran rather than silently falling
back to the path it is compared against.

To capture the child server's logs for that assertion, add an optional
RustFSTestEnvironment.capture_log_path (default None = inherit stdio,
backward compatible) that redirects the spawned server's stdout+stderr to a file.

Co-authored-by: heihutu <heihutu@gmail.com>

crates/e2e_test/src/lib.rs

@@ -32,6 +32,11 @@ mod reliability_disk_fault_test;
 #[cfg(test)]
 mod degraded_read_eof_regression_test;
 
+// backlog#1183: GET codec-streaming fast path must be byte/header identical to
+// the legacy duplex path before its rollout gates can be flipped on by default.
+#[cfg(test)]
+mod get_codec_streaming_compat_test;
+
 #[cfg(test)]
 mod version_id_regression_test;