[Fleet] Display package verification status

[hop-dev]

Summary

Part of #133822

if the package verification feature flag is enabled, show which packages are unverified in the UI:

• show unverified label on the package card in installed integrations (this is not shown in the browse view)
• show a callout in the installed integrations view if any packages are unverified
• show a warning icon on the installed integrations tab if any packages are unverified
• show a callout on the integration overview page if a package is unverified

Additional changes:

• add error.attributes.type to the error response when verification fails so that verification error can be distinguished
• add package_verification_key_id to the fleet status response

NOTE: there are a few TODOs in the code where I will need to add a documentation link when its available, I don't know what other people do when a link isn't ready yet?

Screenshots

Installed integrations: new labels, callout and icon on tab

Tab icon still visible when not on tab:

Callout also displayed on integrations overview:

Testing steps

• 1. Run the version of the EPR with package signatures locally:

docker run -p 8080:8080 docker.elastic.co/observability-ci/package-registry/distribution:PR-463

• 2. set xpack.fleet.registryUrl: http://localhost:8080
• 3. download this public key which will cause all verifications to fail NOT_THE_ELASTIC_KEY
• 4. set xpack.fleet.packageVerification.gpgKeyPath: /tmp/NOT_THE_ELASTIC_KEY.txt
• 5. Enable the feature by setting:

xpack.fleet.enableExperimental: 
    - packageVerification

• 6. force install some packages (force is required to override the verification failing)

Checklist

Delete any items that are not applicable to this PR.

• 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
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[hop-dev]

Not sure if the key ID is out of place on the status endpoint, I contemplated having it on its own endpoint but that also seemed excessive for one value which is unchanging and almost like config.

[juliaElastic]

Code LGTM

[kpollich]

Couple minor comments but overall LGTM 🚀

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 30ecf43
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• FTR Configs #46

Test Failures

• [job] [logs] FTR Configs #46 / Kibana Spaces Accessibility a11y test for delete space button

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
fleet	735	737	+2

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	1381	1389	+8

Async chunks

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

id	before	after	diff
fleet	844.4KB	846.9KB	+2.5KB

Page load bundle

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

id	before	after	diff
fleet	111.3KB	111.6KB	+344.0B

Unknown metric groups

API count

id	before	after	diff
fleet	1513	1521	+8

History

• 💛 Build #56259 was flaky c867a12b0181c4334303fc9e5f9a5aa9314b85a3
• 💚 Build #56099 succeeded 162691626d2a5fcdaa509587c3ceba6062fd2abd
• 💔 Build #56091 failed 0a17655c4f48deeee70ae47da3d01287748b24e3
• 💔 Build #56012 failed 0d1a1f4a4189bc2f5a08f77403ed59d653cc1b81

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

cc @hop-dev