[docs] Add context to Windows integration documentation

[colleenmcginnis]

What does this PR do?

From elastic/observability-docs#1019:

Let's audit the documentation for our top 5 integrations. The descriptions can be improved so users have a better understanding of what benefit they offer, how Elastic can help with the user's use case, and persuade them to install the integration.

This PR adds more context the Windows integration including:

• Applies a new proposed structure to be applied across top integrations (overview, data types, requirements/prerequisites, setup, reference).
• Creates a soft division between guide-like content and reference-like content.
• Adds context to the "Overview":
  • Acknowledges the relationship between this integration and the larger ecosystem of Elastic products.
  • Provides a basic example to illustrate how this integration may be useful.
• Adds a "Data types" section:
  • Provides a high-level overview of the kind of data that is collected. (It's difficult to derive a summary from just the reference sections since they're so long.)
  • Reinforces what "Logs" and "Metrics" are in the context of the integration.
• Adds a "Requirements" section:
  • Reinforces how this integration fits into the larger Elastic system.
  • Mentions that different permission levels may be required for various datasets, but prompts the reader to see the reference sections for detail instead of listing permission information here.
• Points the reader to the Getting started guide for step-by-step "Setup" instructions.

For the reviewer

• I had trouble coming up with a more specific example, but maybe that's ok?
• We say that some datasets "may require dedicated permissions", but we don't provide any details. Are there details we can add that are similar to those in the System integration documentation?
• Open to any and all feedback on language and truthiness!

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• Review by @bmorelli25
• Review by TBD (Integrations team)

Related issues

• Audit top 5 integration overviews observability-docs#1019

[bmorelli25]

Haven't tested the build yet, but everything looks good. One small nit.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-06-21T19:20:55.440+0000

• Duration: 17 min 50 sec

Test stats 🧪

Test	Results
Failed	0
Passed	126
Skipped	0
Total	126

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (4/4)	💚
Files	87.5% (7/8)	👎 -9.06
Classes	87.5% (7/8)	👎 -9.06
Methods	84.884% (73/86)	👎 -4.045
Lines	93.376% (4962/5314)	👍 3.425
Conditionals	100.0% (0/0)	💚

[andrewkroh]

The permissions requirements seem odd to mention because AFAIK the whole Elastic Agent is required to run as a service account which has elevated permissions.

[colleenmcginnis]

I included this because in the System integration, there are different levels of permission needed for different data streams (see this PR), but if that's not the case for the Windows integration I can remove these!