chore(docs): clarify ES rollover standalone binaries and ILM workflow (#1068)

## Which problem is this PR solving?

Addresses jaegertracing/jaeger#7994

The Elasticsearch storage documentation currently shows
Docker-based examples for `jaeger-es-rollover` and
`jaeger-es-index-cleaner`, which may imply that Docker is required.

Additionally, it may not be clear that ILM is an alternative
to the manual rollover + lookback + index-cleaner workflow.

## Description of the changes

This PR:

1. Adds a clarification that `jaeger-es-rollover` and
   `jaeger-es-index-cleaner` are available as standalone binaries
   on the GitHub releases page and are not limited to Docker usage.

2. Clarifies in the ILM section that ILM is an alternative
   to the manual rollover workflow, rather than an additional step.

## How was this change tested?

Documentation-only change. Verified formatting locally
and ensured Hugo shortcodes remain intact.

## Checklist

- [x] I have read
https://github.com/jaegertracing/jaeger/blob/main/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] No code changes (documentation only)
- [x] Formatting verified

## AI Usage in this PR
See [AI Usage
Policy](https://github.com/jaegertracing/jaeger/blob/main/CONTRIBUTING_GUIDELINES.md#ai-usage-policy).
- [ ] **None**: No AI tools were used in creating this PR
- [x] **Light**: AI provided minor assistance (wording and formatting
suggestions)
- [ ] **Moderate**: AI helped with code generation or debugging specific
parts
- [ ] **Heavy**: AI generated most or all of the code changes

---------

Signed-off-by: Omkar ugalmugle <155310707+Omkar-Ugal@users.noreply.github.com>
Signed-off-by: Yuri Shkuro <github@ysh.us>
Co-authored-by: Yuri Shkuro <github@ysh.us>

Author: Omkar-Ugal

content/docs/v2/_dev/storage/elasticsearch.md

@@ -46,6 +46,12 @@ To learn more about rollover index management in Jaeger refer to this
 
 For automated rollover, please refer to [Elasticsearch ILM support](#ilm-support).
 
+{{< info >}}
+The examples for `jaeger-es-rollover` and `jaeger-es-index-cleaner` tools below are shown using
+Docker invocations, but they are also available as standalone binaries on the
+[Jaeger GitHub releases page](https://github.com/jaegertracing/jaeger/releases).
+{{< /info >}}
+
 ### Initialize
 
 The following command prepares Elasticsearch for rollover deployment by creating index aliases, indices, and index templates:
@@ -102,6 +108,11 @@ docker run -it --rm --net=host \
 
 [Elasticsearch ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html) automatically manages indices according to performance, resiliency, and retention requirements.
 
+ILM support is an alternative to the manual rollover + lookback +
+index-cleaner workflow described above. When ILM is enabled,
+Elasticsearch manages rollover and retention automatically
+according to the configured policy.
+
 For example:
 * Rollover to a new index by size (bytes or number of documents) or age, archiving previous indices
 * Delete stale indices to enforce data retention standards