[ILM] Remove frozen phase

[jloleysens]

Summary

After elastic/elasticsearch#62403 was merged, this PR removes the corresponding ILM frozen phase UI.

How to test

1. Start Kibana on basic license
2. Go to index lifecycle management
3. Create a policy with the available form controls for all available phases
4. The form should work as usual, except there should be no option to activate or configure anything regarding a frozen phase.

Additional context

• Undoes work introduced here: [ILM] Add support for frozen phase in UI #75968
• Happens after [ILM] Data tiers for 7.10 #76126 so code grew slightly

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[yuliacech]

Hi @jloleysens, great job on removing Frozen phase (it's a pity it has to go though).
Tested locally, everything works! I searched for frozen and found following usage still in the code that you might want to check:

• /public/extend_index_management/index.js line 202 has a filter option for frozen phase
• snapshots for index management extension
• NodeDataRole type in /common/types/api has data_frozen

[jloleysens]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e32ae72

Build metrics

@kbn/optimizer bundle module count

id	value	diff	baseline
indexLifecycleManagement	205	-2	207

async chunks size

id	value	diff	baseline
indexLifecycleManagement	228.0KB	-14.3KB	242.4KB

page load bundle size

id	value	diff	baseline
indexLifecycleManagement	232.2KB	-309.0B	232.5KB

History

• 💚 Build #75508 succeeded dafc1ce

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

[jloleysens]

Thanks for the review @yuliacech !

Noted; those entries refer to the "frozen" indices as a result of the "freeze" action. That functionality is for adding a label next to those index names in index management so we want them to stick around.