[Index Management] Update the columns width in the index templates and component templates tables

[yuliacech]

Summary

Fixes #174946

This PR tries to improve the readability of the index templates and component templates lists by setting the columns with text information to be wider and to not truncate the text. The badges in the name columns are also set to inline which makes the word breaking in the columns better imho. See screenshots with before and after on a smaller screen (just before the tables switch from rows to a mobile view).

Screenshots

Index templates

Before

After

Component templates

Before

After

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

[yuliacech]

/ci

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[sabarasaba]

Changes lgtm, didnt test locally 🚀

My only feedback is regarding index templates, you can indeed read all the values now but we went from a compact table to one with extremely tall rows. I'd argue that perhaps in smaller screen devices not all columns need to be present since they can be explored in the details flyout. I think the "components" column could perhaps be hidden in order to improve legibility of the data and make it tidier, since right now with all the limited space and text-wrapping it makes it quite hard to follow 🤔

[yuliacech]

Thanks a lot for the feedback, @sabarasaba! Indeed, the Index templates table is now too tall, so I've put back the line truncateText: true on the Components column. I think a better solution might be just to display a number of components and add a link to the Component templates list with a corresponding filter enabled, similar to linking backing indices of a data stream. I'll open an issue for that and address in a separate PR (issue opened here).

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 8553351

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	587.3KB	587.4KB	+82.0B

History

• 💚 Build #189578 succeeded d2fb06a
• 💚 Build #188984 succeeded 12233c5

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