[Lens] Add new Metric formatter migrations

[dej611]

Summary

Part of 54306
Required #158468 to be merged first.

This PR integrates only the migration part of the new Metric new formatter task.

This migration implementation defines takes the simplest route for the migration route of metric visualization formatter:

• if any custom formatter is set in Lens, then apply a compact flag on it to keep it consistent
• if Default formatter is set in Lens, then assume nothing and let the regular formatter hierarchy do its own work

Example

Original dashboard

After migration

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/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[stratoula]

Changes LGTM, I tested locally with some of my dashboards and it works fine!

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 4db8402

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	13	15	+2
securitySolution	410	414	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	14	16	+2
securitySolution	493	497	+4
total			+6

History

• 💚 Build #135135 succeeded 8c4c9cf
• 💔 Build #134726 failed 95023fe
• 💔 Build #134631 failed cf52dd9

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