[8.13](backport #4846) [windows] if elastic-agent run fails, log error to Application EventLog

[mergify]

What does this PR do?

On Windows if the run command fails, then the error message will be sent to the Application EventLog. Other OSes do not require this since they capture stderr from processes that run as services, Windows does not.

This is only for the run command because the other commands should be run from the CLI, where the error is already published on stderr.

Why is it important?

If any error happens before the elastic-agent internal logging is setup and the run command exits while running as a Windows service, the error is lost. Without this error it is very difficult to determine why elastic-agent run is failing.

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. Install elastic-agent with -a flag pointing to CA certificates on the local filesystem
2. Stop elastic-agent service
3. Rename the CA certificates
4. Try to start elastic-agent service
5. Verify that Application EventLog has event showing that elastic-agent failed and what the error was.

Related issues

• Closes [windows] capture early start-up errors #4627

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?
• ...

Screenshots

---

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

[mergify]

Cherry-pick of 6c20730 has failed:

On branch mergify/bp/8.13/pr-4846
Your branch is up to date with 'origin/8.13'.

You are currently cherry-picking commit 6c20730d5c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1717516439-Capture-early-errors-on-Windows.yaml
	new file:   internal/pkg/agent/cmd/run_unix.go
	new file:   internal/pkg/agent/cmd/run_windows.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   internal/pkg/agent/cmd/run.go
	both modified:   internal/pkg/agent/install/install_windows.go
	both modified:   internal/pkg/agent/install/uninstall.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[pierrehilbert]

We are not planning to release new 8.13 binaries so I'm closing this one.

[elastic-sonarqube]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 40%)

See analysis details on SonarQube

[mergify]

This pull request has not been merged yet. Could you please review and merge it @leehinman? 🙏

[jlind23]

@leehinman unsure why you reopened this but no more 8.13 patch release will be made.