Fix ownership of component specs in elastic-agent docker image

[pchila]

What does this PR do?

Fix ownership of components' spec files in <agent install dir>/data/elastic-agent-<commit>/components/*.yml from root:root to <user>:<user> where user is the default user the agent process will be started with

Why is it important?

To prevent permissions mismatches between component binaries and their spec yaml files under ../components

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

Related issues

• Closes [Fleet]: Hosted fleet server gets unhealthy on 8.16 Snapshot. #5615

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]

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

[mergify]

This pull request does not have a backport label. Could you fix it @pchila? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[jlind23]

CI will be failing until this is reverted - elastic/beats#40980
cc @ycombinator

[pchila]

/test

[pchila]

@jlind23 @ycombinator elastic/beats#40980 has been merged (I assume that this was the revert @jlind23 referred to) but there are still a lot of leak/integration/serverless test failures...

While having TestAPMConfig fail can be expected (especially since apm server is not healthy) shouldn't the other failures disappear after merging elastic/beats#40980 ?

[jlind23]

@pchila You should be able to rebuild it and it will go away. The problem was fixed only a few minutes ago once the new unified release was available.

[pchila]

/test

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[ycombinator]

We need this change for Integrations Server on ESS to spin up without errors and the CI failures are unrelated to this PR. So force merging...