[DOCS] Osquery features in 8.5

[nastasha-solomon]

Addresses #2522, #2513, and #2512.

Previews:

• Create a detection rule - Made a couple changes to this topic:
  • Added a seventh step to the list of steps for creating a new rule. Scroll to the end of the intro para to find the steps.
  • Fixed the heading of the section for Use value lists with indicator match rules.
  • Set up response actions - New section
• View alert details - Added a new section for the Osquery Results tab.
• Osquery - New topic
  • Add Osquery response actions - New topic
  • Run Osquery from investigation guides - New topic
  • Run Osquery from alerts - Added requirements and removed content about viewing query results (created a new topic for this)
  • Examine Osquery results - Somewhat new topic. Wrote new intro and renamed first three sections.

[github-actions]

Documentation previews:

• ✨ HTML diff
• 📙 Elastic Security Guide

[joepeeples]

Lots of great stuff here, and a massive effort, thank you!

One general, big-picture question: Does this new "Use Osquery" section still belong inside the "Detections and alerts" parent section? With these new features (and more on the way I assume), It seems like Osquery cuts across several functions, not just detections & response but also investigation, threat hunting, etc. Maybe this should be a top-level section of its own?

[jmikell821]

Lots of good changes here! One tiny tiny nit, then Joe had a question here. Other than that, I won't nit pick at this one further because I know it was a big PR. Thanks for pulling this together. 🌟

[mergify]

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b osquery-8.5-features upstream/osquery-8.5-features
git merge upstream/main
git push upstream osquery-8.5-features