[EDR Workflows] Initialize SelectorComponent value in Scripts picker

[tomsonpl]

Description

Previously, #204965 introduced a string based Selector Component, however the Response Console's framework wasn't adjusted to fully support it:

• Selector Components Not Restoring State from History:
  When users selected a command from history (e.g., custom script execution), the selector UI (such as script dropdowns) could not restore its value from the previously entered command text. This left the UI out of sync with the command, confusing users and breaking workflows.

• Broken Paste Functionality:
  Pasting a full command (including arguments meant for selectors) into the console did not populate the selector UI components. As a result, users who pasted commands from documentation or shared snippets would see empty or incorrect selector states, making it difficult to execute or edit those commands.

These issues stemmed from the lack of a unified mechanism for synchronizing between the command text and selector state. Command-specific logic was difficult to maintain and extend.

---

How was it resolved?

This PR introduces a unified, handler-based approach to command parsing and selector state management:

• Command Handlers:
  Each supported command (e.g., runscript) now has a dedicated handler responsible for:

  • Initializing selector state from command text (for both history and paste)
  • Reconstructing command text from the current selector state (for editing and display)
  • Keeping the UI and command text in sync at all times

  Note: For file upload, the selector is always initialized as empty, matching the intended UX.

• Central Registry:
  All command handlers are registered in a central registry, allowing the system to dynamically delegate parsing and state management to the correct handler for each command. This eliminates scattered logic and makes the system much more maintainable.

• Bidirectional Synchronization:
  Selector components now reliably initialize their state from both command history and pasted text (where applicable). Any changes in the selector UI are immediately reflected in the command text, and vice versa.

---

Additional Architectural Improvements

Based on code review feedback, this PR also addresses architectural concerns with the CustomScriptSelector component:

• 🔧 Standard React Component:
  Converted from function-returning-component pattern (CustomScriptSelector('agentType')) to standard React component (<CustomScriptSelector />)

• 🔧 Console Framework Encapsulation:
  Removed direct useConsoleStateDispatch() coupling and replaced with proper callback-based architecture (onChange, requestFocus)

• 🔧 Command Metadata Integration:
  Agent type now extracted from command.commandDefinition.meta?.agentType instead of function parameters, following console framework patterns

• 🔧 Enhanced Interface:
  Added command: Command and requestFocus?: () => void props to CommandArgumentValueSelectorProps for better component integration

These changes ensure the console remains a generic, maintainable framework while providing clean interfaces for selector components.

---

Result

• Selector UI components now always reflect the correct state when loading from history or after pasting a command (for commands where this is supported).
• Users can confidently copy, paste, and re-run complex commands with selector arguments.
• The codebase is more maintainable and ready for future extension.
• Console framework maintains proper encapsulation with well-defined component interfaces.

Screen.Recording.2025-06-27.at.12.15.47.mov

Closes: #225269
Closes: #225407

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[tomsonpl]

/ci

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 972b823

Failed CI Steps

• FTR Configs #70

Test Failures

• [job] [logs] FTR Configs #70 / Actions and Triggers app Connectors General connector functionality should delete a connector

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	7850	7855	+5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	9.8MB	9.8MB	+2.6KB

History

• 💛 Build #315858 was flaky 5fc2069
• 💔 Build #315844 failed 32aa098
• 💔 Build #315828 failed 82d6b27
• 💔 Build #315532 failed 4bbd14b
• 💚 Build #315387 succeeded 754f02c
• 💔 Build #315319 failed e41b63e

cc @tomsonpl

[elasticmachine]

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

• Click to trigger kibana-pull-request for this PR!
• Click to trigger kibana-deploy-project-from-pr for this PR!
• Click to trigger kibana-deploy-cloud-from-pr for this PR!

[tomsonpl]

closing in favor of: #227463