[Index Management] Add deprecation warning to index template and component template UIs

[sabarasaba]

Partially addresses #170805

Summary

With elastic/elasticsearch#101148 we now can alert the users when a component template or index template will soon be deprecated and shouldnt be relied upon. This PR adds a badge and a callout to the component template and index template UIs to alert the users about this.

How to test

• Start up kibana and es
• Navigate to Stack management -> index management (component_templates|index_templates)
• Verify that:
  • Deprecated resources are hidden by default
  • Upon enabling filtering to see them they should pop up on the table with a badge
  • Verify that deprecated resources are highlighted and when editing, we also show a warning callout.

Create deprecated component template

PUT _component_template/template_1
{
  "template": {
    "settings" : {
        "number_of_shards" : 1
    }    
  },
  "deprecated": true
}

Screenshots

// index templates

// component templates

[sabarasaba]

/ci

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

/ci

[sabarasaba]

/ci

[sabarasaba]

/ci

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

/ci

[elasticmachine]

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

[sabarasaba]

@elasticmachine merge upstream

[yuliacech]

Thanks a lot for working on this, @sabarasaba!
Code changes LGTM and locally the badges work as expected. As already discussed, we should decide together with the team on how to handle the filters and hiding/showing the items in the table consistently. The component templates filters have the same issue as ingest pipelines.
Other than that I noticed that both index templates and component templates tables have issues with column widths. I opened an issue for that, maybe it's a regression we haven't noticed after an update or similar. But I think the badges in component templates should stack when there are several of them, wdyt? (see screenshot below)

[sabarasaba]

@elasticmachine merge upstream

[kibanamachine]

merge conflict between base and head

[sabarasaba]

@elasticmachine merge upstream

[yuliacech]

Thanks a lot for addressing the feedback, @sabarasaba!
I re-tested locally and pushed some changes for component templates: similar to ingest pipelines, I don't think we need to add "fuzzy matching" because the table handles the search automatically.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f920010

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
indexManagement	604	607	+3

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
indexManagement	210	218	+8

Async chunks

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

id	before	after	diff
indexManagement	588.9KB	593.2KB	+4.3KB

Unknown metric groups

API count

id	before	after	diff
indexManagement	215	223	+8

History

• 💔 Build #191326 failed cb91c62
• 💔 Build #191207 failed ac227d0
• 💔 Build #190654 failed de90607
• 💛 Build #187356 was flaky e4c4ea5
• 💚 Build #186996 succeeded 0100c5c

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

cc @yuliacech