[Index Management] Add number formatting to the indices list

[yuliacech]

Summary

Fixes #22173
This PR adds a formatting to the index size column of the indices list. The number formatting is done according to the default locale in the browser. I decided against aligning the column right because this would looked misaligned to other columns. And aligning all of the columns right doesn't look good either (see screenshots).

Screenshot

Formatted index size

Aligning the size column right (not implemented)

Aligning all columns right (not implemented)

Checklist

• 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/platform-deployment-management (Team:Deployment Management)

[sabarasaba]

Nice enhancement, I dont think we do this often enough in our UIs! Changes lgtm, tested locally.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 6032cff

Failed CI Steps

• Osquery Cypress Tests #4

Test Failures

• [job] [logs] Osquery Cypress Tests #4 / ALL - Inventory should be able to run the previously saved query should be able to run the previously saved query
• [job] [logs] Osquery Cypress Tests #4 / ALL - Inventory should be able to run the query should be able to run the query

Metrics [docs]

Async chunks

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

id	before	after	diff
indexManagement	562.1KB	562.1KB	+46.0B
securitySolution	12.8MB	12.8MB	+6.4KB
securitySolutionServerless	329.8KB	336.0KB	+6.3KB
total			+12.7KB

Page load bundle

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

id	before	after	diff
securitySolutionServerless	41.6KB	41.6KB	-1.0B

History

• 💔 Build #171518 failed e6dd902

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