[8.18] (backport #9560) Fix/5871 redact secrets in diagnostics

[mergify]

• Bug

What does this PR do?

Updates diagnostics redaction process to redact secrets from pre-config, computed-config, components-expected and components-actual files in the diagnostics archive

Why is it important?

This pr increases the scope of the redaction to all files where they may be exposed

Checklist

• I have read and understood the pull request guidelines of this project.
• 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

none

How to test this PR locally

• Build the agent
• Create policy with integrations that have secrets, I used aws-cloudwatch
• Enroll the agent
• Request diagnostics
• Validate that the secrets are redacted

---

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

[mergify]

Cherry-pick of a44e87a has failed:

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

You are currently cherry-picking commit a44e87a24.
  (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/1756122869-update-secret-redaction-in-diagnostics.yaml
	modified:   internal/pkg/agent/application/coordinator/coordinator.go
	modified:   internal/pkg/agent/cmd/inspect.go
	modified:   internal/pkg/diagnostics/diagnostics.go
	modified:   internal/pkg/diagnostics/diagnostics_test.go
	modified:   testing/integration/ess/diagnostics_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   internal/pkg/agent/application/coordinator/coordinator_unit_test.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

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elastic-sonarqube]

Quality Gate passed

Issues
2 New issues
1 Fixed issue
0 Accepted issues

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

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 2c9b93d

History

• 💔 Build #25800 failed 93647c8

cc @kaanyalti

[mergify]

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