[Data Streams] Fix displayed index mode

[ElenaStoeva]

Fixes #208671

Summary

Before this PR, the displayed index mode of the data streams was determined based on the index mode of the associated index template. However, the index mode can also be set through the component template, so that logic is not reliable and can cause incorrectly displayed index mode like described in #208671.

In this PR, we replace this logic with the recently added index_mode field to the Es Get Data Streams API (see elastic/elasticsearch#122486).

How to test:

1. Create a component template with a LogsDB index mode (you can also test with other index modes):

PUT _component_template/my-component-template
{
  "template": {
    "settings": {
      "index": {
        "mode": "logsdb"
      }
    }
  }
}

2. Create an index template that is composed of the component template above:

PUT _index_template/my-index-template
{
  "index_patterns": [
    "my-ds-*"
  ],
  "data_stream": {},
  "composed_of": [
    "my-component-template"
  ]
}

3. Create a data stream that matched the index pattern from the index template above:

PUT _data_stream/my-ds-1

4. Go to the data streams table and verify that the index mode is displayed correctly in the table.

5. Click on the created data stream and verify that the displayed index mode in the details panel is correct:

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)

[ElenaStoeva]

Marking as a draft for now as I noticed that the index mode field from the Es API is not behaving as expected - it doesn't get updated after we update the index mode of the index template/component template:

Screen.Recording.2025-03-25.at.11.01.33.mov

Will follow up on this.

[ElenaStoeva]

Reopening as it's okay if the displayed index mode is not immediately updated after a change of index mode of the index template as per discussion with @elastic/es-data-management.

[SoniaSanzV]

@elasticmachine merge upstream

[SoniaSanzV]

tested locally, lgtm :)

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 6186c6f

Failed CI Steps

• Jest Integration Tests #1
• FTR Configs #40

Test Failures

• [job] [logs] FTR Configs #40 / security APIs - Login Selector Login Selector SAML should be able to have many pending SP initiated logins all successfully succeed

Metrics [docs]

✅ unchanged

History

• 💔 Build #293351 failed e1b0624
• 💔 Build #293220 failed 211eff0
• 💚 Build #291492 succeeded 973ef80
• 💔 Build #291231 failed 93e1b5c
• 💔 Build #291111 failed 144e5ca

cc @ElenaStoeva

[kibanamachine]

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15170415637

[kibanamachine]

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15170415587

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation