fix(git): preserve patch output from log commands

[kingpy-bot]

Summary

• treat -p, -u, --patch, --patch-with-raw, and --patch-with-stat as explicit requests for raw git log output
• stream the exact Git output instead of injecting RTK formatting, count, or merge defaults and then filtering away patch bodies
• keep the existing compact path unchanged for non-patch log invocations

Closes #2944.

Testing

• cargo fmt --all -- --check
• cargo clippy --all-targets -- -D warnings
• cargo test --all (2,496 passed; 8 ignored)
• end-to-end regression asserts rtk git log -p --all byte-matches raw Git and preserves a searched test-key marker

AI-assisted contribution.

[CLAassistant]

All committers have signed the CLA.

[kamusmg]

Built this branch and ran the #2944 repro against it — it does what it claims. With a 300-line diff and the secret at ~line 152 of the hunk:

command	real git	this branch
git log -p	1 hit	1 hit	✅
git log --all -p	1 hit	1 hit	✅
git show HEAD	1 hit	0	out of scope here
git diff HEAD~1	1 hit	0	out of scope here
git stash show -p	1 hit	0	out of scope here

So this closes the log half cleanly. The remaining paths still route through compact_diff, so #2944 stays open after this merges — details and fixture in my comment there.

One note on the test in this PR, meant to help rather than block: compact_diff caps at 100 lines per hunk, so a fixture whose payload sits near the top of the hunk passes even with the bug present. I hit that myself — my first run "cleared" git show and git stash show for exactly that reason. Placing the payload past line 100 of the hunk makes the test fail for the right reason if the passthrough ever regresses.

(Verified on Windows / x86_64-pc-windows-gnu, develop @ 5d32d07 + 0baf07e.)

[KuSh]

LGTM! Thanks for your contribution