updating managed agent manifest needed resources for cloudbeat

[oren-zohar]

Summary

agent manifest needs more mounts and kube-api resources permissions for some of cloudbeat fetchers to work properly, see:

• https://github.com/elastic/security-team/issues/3683
• https://github.com/elastic/security-team/issues/3682
• [Fleet] Display k8 deployment instructions in fleet mode #92113

additionally, since cloudbeat will require custom agent deployment (like the Kuberentes package) we'll need to add our package into the custom agent manifest flow, where the user is promoted with a new manifest with the relevant permissions for the managed agent deployment

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[juliaElastic]

LGTM

[oren-zohar]

note: merge only after this PR is merged

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: be726fc
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• Fleet Cypress Tests

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
fleet	1274	1275	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	702.4KB	702.4KB	+58.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	90.3KB	90.4KB	+137.0B

Unknown metric groups

API count

id	before	after	diff
fleet	1393	1394	+1

History

• 💔 Build #41823 failed c67c31e
• 💛 Build #41072 was flaky dbf7949
• 💚 Build #40932 succeeded a2ef6d2
• 💚 Build #40388 succeeded 6c0a574
• 💔 Build #40180 failed a67560b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream