[8.x](backport #6410) Add logging to EventLog for error, install, uninstall

[mergify]

What does this PR do?

On Windows, if the install, uninstall, or enroll commands fail, they will now attempt to add the error to the Windows Application Event Log. This is the same behavior that the run command has.

Why is it important?

If any of these commands are done with automation it can be difficult to capture the errors that appear on standard error. This gives us a chance of capturing the error and reviewing later.

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/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

1. Build with this PR
2. Run Install
3. Try to uninstall with bad arguments or a file open in the install directory
4. Error should be visible in the Event Viewer

Related issues

• Closes Add logging to Event Log for install, uninstall, and enroll subcommands #6338

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

This is an automatic backport of pull request #6410 done by [Mergify](https://mergify.com).

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube