[ILM] Index Lifecycle Policies show wrong unit in Kibana UI

[simitt]

Kibana version: 7.0.1

Elasticsearch version: 7.0.1

Describe the bug:
Setting up index policies with min_age, max_age or max_size using small time units or byte size units as described in the docs leads to unexpected behavior, when navigating to Index Lifecycle Policies in Kibana. It shows the configured values, but with different units, as the configured units are not available in the UI.

Steps to reproduce:

1. Setup ILM policy with time unit second and byte size unit kb.
2. Navigate to Kibana Management/Elasticsearch/Index Lifecycle Policies and click on the configured policy. This shows a wrong unit for the configured options.

Expected behavior:
See configured units.

Screenshots (if relevant):
Units shown in the UI:

Configuration in json:

[elasticmachine]

Pinging @elastic/es-ui

[eedugon]

Note also that when the described issue occurs, if the user updates the value (not the unit), Kibana will update the value of the policy but keeping the old unit, which creates a lot of confusion.
On the other hand, if the unit is changed to hours and then back to days (without needing to save) and then it's saved, then the internal policy changes the unit and all gets aligned.

[alisonelizabeth]

Fixed via #55228