Set minimum rollover conditions in ILM policies

## Summary

Kibana PR #270398 adds a redesigned hot-phase rollover editor in the ILM policy UI that separates rollover triggers (`max_*`) from rollover restrictions (`min_*`). Users can configure `min_age`, `min_docs`, `min_size`, `min_primary_shard_docs`, and `min_primary_shard_size` alongside existing maximum triggers, and the policy flyout displays configured minimum conditions. The Elasticsearch rollover action reference already documents these fields, but the Kibana how-to pages that walk through the policy editor still describe rollover using only maximum trigger conditions.

**Why this needs docs:** The API reference is current, but the primary Kibana policy-creation workflow omits the new minimum-restriction UI that ships in 9.5.0; the PR includes six screenshots that would help update those pages but should not be added by this triage pass.

## Resources

- PR [#270398](https://github.com/elastic/kibana/pull/270398) — [ILM] Add min_* rollover fields
- Product issue: https://github.com/elastic/kibana/issues/217860

Screenshots from PR


## Availability

| Channel | Details |
|---------|---------|
| **Stack** | v9.5.0 |
| **Serverless** | N/A |
| **Feature flag** | None — active by default |

---
*Created with [Docs Quest Scanner](https://github.com/florent-leborgne/docs-quest-scanner) by @florent-leborgne*

## Suggested edits

[Create an index lifecycle management policy in Elasticsearch](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy) > Create a lifecycle policy > Kibana tab (Hot phase rollover step)
- **What the docs say:** Step 4 describes the hot-phase rollover action using recommended defaults (30 days, 50 GB primary shard) and says to disable **Use recommended defaults** to adjust values or roll over based on primary shard size, primary shard document count, or total index document count—covering only maximum trigger conditions.
- **What to add:** The Kibana tab does not document the redesigned rollover editor that separates rollover triggers from rollover restrictions, or how to set `min_age`, `min_docs`, `min_size`, `min_primary_shard_docs`, and `min_primary_shard_size` in the hot phase; update this create-policy workflow to match the 9.5.0 UI. Stack only, from 9.5.0 (not available in serverless).

[Index rollover and routing allocation in Elasticsearch](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/rollover) > How rollover works in ILM
- **What the docs say:** States that rollover runs when any configured conditions are met and lists only size, age, and document count as rollover conditions; it mentions `min_docs: 0` only in the empty-index special rule, not as part of a general minimum-restriction model.
- **What to add:** This conceptual section does not explain that rollover uses maximum triggers together with optional minimum restrictions (`min_*`), leaving readers who land here before the policy editor without guidance on preventing premature rollovers or many small shards. Stack only, from 9.5.0 (not available in serverless).

Start with the “Create an index lifecycle management policy in Elasticsearch” page, especially the Kibana tab’s Hot phase rollover step, then review “Index rollover and routing allocation in Elasticsearch” and the linked PR #270398. Update both sections to explain the redesigned editor’s maximum triggers and optional min_* restrictions for Stack 9.5.0, covering the listed minimum conditions without adding screenshots. Verify that the workflow and conceptual explanation match the current UI and API behavior.

Written by the indexing model from the issue text.