Add fips attribute to agent metadata sent to fleet

[michel-laterman]

What does this PR do?

Add elastic.agent.fips (bool) attribute to local_metadata sent with enroll and checkin requests.
The value of this attribute indicates if the agent is a FIPS compliant distribution.

Why is it important?

elastic-agent needs to be able to signal to fleet-server if it is running a FIPS distributable.

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

N/A

[elasticmachine]

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

[jlind23]

@michel-laterman seems like unit tests need to be updated to add the fips field in the expected json.

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: a202694

Failed CI Steps

• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Windows 2022
• Unit tests - Windows 2022
• Unit tests - Windows 2016
• Unit tests - macOS 15 ARM
• Unit tests - macOS 15 ARM
• Unit tests - Windows 10
• Unit tests - Windows 11

History

• 💚 Build #17957 succeeded 87b2f86
• 💔 Build #17824 failed 30d5fca
• 💔 Build #17822 failed e66f00d

cc @michel-laterman

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube