[Agent] Allow to debug agent configuration

[ph]

When the user needs to troubleshoot a problem with an Agent, they need to know exactly what is running. They should be able to see the agent version, version of all binaries (FB/MB), and the version of agent config in both the current configuration and pending updates. It doesn’t matter how the user accesses this information as long as it’s available (files, CLI command, logs).

[elasticmachine]

Pinging @elastic/ingest-management (Team:ingest-management)

[ph]

After looking at it, I will remove the local obfuscation to allow users to read the content locally, there are no easy way to completely and safely keep secrets locally.

[ph]

This is linked to #17389, there is indeed an issue with how with persist data locally and how we are invalidating that data.

[ph]

Debug:

• action_store.yml contains the last configuration and is not encrypted.
• fleet.yml contains the api keys and kibana host information and is not encrypted.

Beats version match the agent version.