Restrict queued-message editing to its dedicated binding (#39064)

## What changed

- Stop treating Vim normal-mode history-up as an alias for editing the latest queued message.
- Continue to edit queued messages through the configured `chat.edit_queued_message` binding.

GitOrigin-RevId: d830e0976a38725e948d420c1a5f374bb13fe945

codex-rs/tui/src/bottom_pane/chat_composer.rs

@@ -44,11 +44,6 @@
 //! - Persistent cross-session history (text-only; no element ranges or attachments).
 //! - Local in-session history (full text + text elements + local/remote image attachments).
 //!
-//! Before composer history handles Vim-normal history-up, `ChatWidget` restores the latest queued
-//! follow-up when the composer is empty and no popup is active. It removes the message from the
-//! queue before placing it in the composer, so editing and requeuing it replaces the prior
-//! revision instead of creating duplicates.
-//!
 //! When recalling a local entry, the composer rehydrates text elements and both attachment kinds
 //! (local image paths + remote image URLs).
 //! When recalling a persistent entry, only the text is restored.

codex-rs/tui/src/bottom_pane/mod.rs

@@ -1222,12 +1222,8 @@ impl BottomPane {
         popup_consts::standard_popup_hint_line_for_keymap(&self.keymap.list)
     }
 
-    pub(crate) fn runtime_keymap(&self) -> &RuntimeKeymap {
-        &self.keymap
-    }
-
     pub(crate) fn list_keymap(&self) -> crate::keymap::ListKeymap {
-        self.runtime_keymap().list.clone()
+        self.keymap.list.clone()
     }
 
     /// Replace one or more active views whose IDs are in `view_ids` with a