Include auto-review rollout in feedback uploads

[won-openai]

Summary

• include the live auto-review trunk rollout when /feedback uploads logs
• upload that attachment as auto-review-rollout-<parent-thread-id>.jsonl so it is distinguishable from the parent rollout
• show the same auto-review attachment name in the TUI consent popup

Scope

• this only covers the live cached auto-review trunk for the current parent thread
• it does not add durable historical parent->auto-review lookup
• it does not add persisted rollout support for ephemeral parallel review forks

UI

Validation

• cargo test -p codex-core cached_guardian_subagent_exposes_its_rollout_path
• cargo test -p codex-feedback
• cargo test -p codex-app-server
• cargo test -p codex-tui feedback_upload_consent_popup_snapshot
• cargo test -p codex-tui feedback_good_result_consent_popup_includes_connectivity_diagnostics_filename

Known unrelated local failures

• cargo test -p codex-core currently fails in the pre-existing proxy env snapshot test tools::runtimes::tests::maybe_wrap_shell_lc_with_snapshot_keeps_user_proxy_env_when_proxy_inactive
• cargo test -p codex-tui currently hits pre-existing status::* snapshot drift unrelated to this change

Follow-Up

• persist parallel auto-review fork sessions so /feedback can include their rollout history too
• attach each persisted fork as its own clearly named file, for example auto-review-rollout--fork .jsonl, instead of merging multiple Guardian sessions into one attachment
• keep the same live-session-only scope initially; durable historical parent -> auto-review lookup can remain a separate decision if we later need feedback from resumed sessions

[dylan-hurd-oai]

quick clarification about FeedbackAttachmentPath, but otherwise looks reasonable!