[Workflows] Document all test-run data options in the YAML editor

[nastasha-solomon]

Summary

Restructures the Supply test input section on the Use the YAML editor page — renamed Provide data for a test run — so all three ways to supply test data are actually explained, not just one:

• Previously, only the Historical option (reuse data from a previous execution) was documented; Document and Manual were listed but never explained.
• Adds a dedicated subsection for each option: Use a document from Elasticsearch, Type your own JSON, and Reuse data from a previous run.
• Documents the time-range filter next to the historical execution picker (defaults to the last week).
• Replaces "input data" with plain language ("data") throughout the section.
• Aligns the test-run dialog name (Test workflow) across the Use the YAML editor, Monitor workflow execution, and Event-driven triggers pages — it was previously called the Run workflow dialog in one place.
• Updates cross-references on the Monitor workflow execution and Event-driven triggers pages to point to the renamed section.

Related to #7350. This PR documents the time-range filter on the historical picker, but doesn't yet cover the anchor-to-selected-run and cleared-selection-when-out-of-range behaviors that issue also asked for.

Previews

• Use the YAML editor | Provide data for a test run: New section explaining all three test-run data options (Document, Manual, Historical).

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes - Claude Code
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/workflows/authoring-techniques/monitor-workflows.md
• explore-analyze/workflows/authoring-techniques/use-yaml-editor.md
• explore-analyze/workflows/triggers/event-driven-triggers.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.