[8.x][Data Usage] New plugin (#193466)

[neptunian]

The initial serverless only plugin for viewing data usage and retention in Management. The purpose of this PR is to provide a place for other engineers to work on it, hidden from public use.

• Plugin is hidden by default and can be enabled through kibana.yml xpack.dataUsage.enabled: true
• Currently it will show up in both stateful and serverless (if enabled using config above). When we are ready to make the plugin available we will enable it in config/serverless.yml
• Renders a card in Management (serverless) when enabled:

#192965
#192966

---

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

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
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• 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)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

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

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[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!)

[neptunian]

/ci

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 480e549
• Interpreting CI Failures

Failed CI Steps

• Jest Tests #8
• Jest Tests #8

Test Failures

• [job] [logs] Jest Tests #8 / SuggestUsersPopover calls onUsersChange when 1 user is selected
• [job] [logs] Jest Tests #8 / SuggestUsersPopover calls onUsersChange when 1 user is selected

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
dataUsage	-	30	+30

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
dataUsage	-	6	+6

Async chunks

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

id	before	after	diff
dataUsage	-	6.7KB	+6.7KB
management	45.9KB	46.1KB	+219.0B
total			+6.9KB

Page load bundle

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

id	before	after	diff
dataUsage	-	4.0KB	+4.0KB
serverless	14.0KB	14.1KB	+168.0B
serverlessObservability	27.0KB	27.2KB	+168.0B
serverlessSearch	20.8KB	21.0KB	+168.0B
total			+4.5KB

Unknown metric groups

API count

id	before	after	diff
dataUsage	-	6	+6

async chunk count

id	before	after	diff
dataUsage	-	1	+1

ESLint disabled in files

id	before	after	diff
dataUsage	-	1	+1

ESLint disabled line counts

id	before	after	diff
dataUsage	-	3	+3

Total ESLint disabled count

id	before	after	diff
dataUsage	-	4	+4

History

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

[delanni]

Just connecting the dots here, this is a backport of #193466