[ML] Enhances support for counter fields in data visualizer / field statistics

[qn895]

Summary

Follow up of #152898 and addresses #153050. This PR adds better support for time series metric counter field. It also temporarily adds a list of supported elasticsearch aggregations for each field type (until elastic/elasticsearch#93884 or equivalent is merged in).

Currently, it will supportcount, min, and max aggs.

It will also not show cardinality instead of showing it as 0 when not available.

It also supports new field types like gauge and counter in the field type filters.

Going to Lens will also use maximum operation instead of average, depending on what the field type supports.

Screen.Recording.2023-03-29.at.13.34.36.mov

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
• 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

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[peteharverson]

The changes here look good, but left a couple of suggestions for follow up work.

[peteharverson]

Tested latest changes and LGTM.

I flipped the release note label to enhancement and edited the PR title.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: c37e8c5

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
dataVisualizer	319	320	+1

Async chunks

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

id	before	after	diff
dataVisualizer	366.3KB	365.6KB	-730.0B

Page load bundle

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

id	before	after	diff
dataVisualizer	25.5KB	21.9KB	-3.6KB

Unknown metric groups

API count

id	before	after	diff
@kbn/ml-agg-utils	90	92	+2

ESLint disabled line counts

id	before	after	diff
securitySolution	432	435	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	512	515	+3

History

• 💚 Build #116887 succeeded f9a6d40
• 💔 Build #116528 failed 04798f9
• 💔 Build #116198 failed 34a7f7f

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

cc @qn895

[alvarezmelissa87]

Code LGTM ⚡