internal/pkg/agent/application/coordinator: fix logging calls

[efd6]

What does this PR do?

Fixes logging calls that expect to be able to interpret formatting verbs.

Why is it important?

Current code is incorrect.

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

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

[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-11-14T22:11:30.172+0000

• Duration: 14 min 55 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

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

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[blakerouse]

Nice catch!

[blakerouse]

buildkite test this

[efd6]

@blakerouse Are you able to force merge this? The integration tests are failing for unrelated reasons.

[cmacknz]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[cmacknz]

Merging, seems like the Windows tests aborted themselves without explanation, I do see the Linux tests passed.

2023-11-14 23:27:48 UTC | >>> (linux-amd64-ubuntu-2204) Test output (sudo) (stdout): >> go test: remote-linux-amd64-ubuntu-2204-sudo.integration Test Passed
-- | --
  | 2023-11-15 03:24:36 UTC | >>> (windows-amd64-2022) non-sudo tests failed: wait: remote command exited without exit status or exit signal
  | 2023-11-15 03:24:36 UTC | >>> (windows-amd64-2022) Failed to execute tests on instance: error running non-sudo tests: failed to fetched test output at %home%\agent\build\TEST-go-remote-windows-amd64-2022.integration.out