x-pack/winlogbeat/module/sysmon: Add event.category and event.type to Sysmon

[kcreddy]

What does this PR do?

• As part of [Windows] Sysmon Operational missing event.category and event.type integrations#5976, adds event.category and event.type to Sysmon module
• Sync fields from windows.sysmon_operational datastream.

Why is it important?

Helps with creating detection rules on ECS fields event.category and event.type

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Closes [Windows] Sysmon Operational missing event.category and event.type integrations#5976

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kcreddy? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[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: 2023-04-25T05:43:53.196+0000

• Duration: 38 min 8 sec

Test stats 🧪

Test	Results
Failed	0
Passed	930
Skipped	9
Total	939

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[kcreddy]

/test

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)