[Fleet] Show multiple agent policies in integrations table

[criamico]

Closes #182111

Summary

Show multiple agent policies in integrations table.

Testing

• Enable feature flag enableReusableIntegrationPolicies
• Install an integration that has more than one agent policies associated with it (instructions are here)
• Navigate to integrations table and verify that the policy displays a badge with the number of associated policies -1 and that it opens up a popover, like in below screenshots.

NOTE the button "Manage agent policies" does not work for now, as the feature is under development and it's hidden with a feature flag!

With feature flag enabled, when integration has multiple agent policies

When one of the policies is managed:

When feature flag not enabled or integration has only one agent policy

The UI remains as it is today:

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[criamico]

This can be implemented with #182112

[juliaElastic]

Looks great! Maybe we could decrease the padding between the list items to be closer to the mockup.

[juliaElastic]

LGTM, left one suggestion

[criamico]

@juliaElastic I fixed the padding, it should be closer to design now. The EuiListGroup component is very customisable so there was no need to override the styles :)

[jen-huang]

nit: is this the right component to use? comparing the designs vs the PR screenshots, seems like using this introduces a lot of extra spacing between the elements. how about using simple <ul> and <li>s instead?

edit: sorry, just saw Julia comment on the same thing. I feel there is probably still room to tighten up the real estate here though

[criamico]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: c6f3fb8

Failed CI Steps

• FTR Configs #83

Test Failures

• [job] [logs] FTR Configs #83 / Fleet Endpoints Integrations inputs_with_standalone_docker_agent "before all" hook for "generate a valid config for standalone agents"

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	1031	1032	+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	1.4MB	1.4MB	+2.4KB

History

• 💔 Build #215765 failed aa2f053
• 💔 Build #215706 failed d1ecfca

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

cc @criamico

[nicpenning]

👀