[Security Solution] Move existing test plans of Rules Management team from Google docs to Kibana repo

[jpdjere]

Epics: https://github.com/elastic/security-team/issues/1974 (internal), https://github.com/elastic/kibana/issues/174168

Summary

Move existing test plans of the Rule Management team from Google docs to the Kibana repo.

All test plans should be created as Markdown files in the x-pack/plugins/security_solution/docs/testing/test_plans/detection_response folder. Scenarios should be written using the Gherkin language. See detection_response/prebuilt_rules/installation_and_upgrade.md for an existing example.

Test plans

The test plans to move are:

• Related Integrations (internal)
• Required Fields (internal)
• Setup Guide (internal)
• Display callout if users have V1/V2 ML Rules installed (internal)
• Bulk Editing of Detection Rules (internal)
• Persistent Rules Table State (internal)
• Rule Snoozing in Security Solution (internal)
• Maintenance Window Callout (internal)

Other (draft or legacy) test plans just FYI:

• New Rule Execution Log UI (internal)
• Bulk Editing of Detection Rules (internal)
• Bulk apply timeline template (internal)
• Bulk Edit Schedule (internal)
• Bulk Add Actions for Multiple Rules (internal)
• Installing / Upgrading Prebuilt Rules ASIS (internal)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)