[WIP] ESQL docs: clarify duration aliases (minute vs month), case-insensitive, optional whitespace

[Zachary-hub]

This is a docs-only change clarifying duration aliases in ESQL.

• month: m/mm; minute: min/mi/n; millisecond: ms
• matching is case-insensitive
• whitespace between number and unit is optional (1m == 1 m)
• examples included

Rationale: adding m as an alias for minute would be ambiguous with m for month
(case-insensitive matching + optional whitespace). Therefore we clarify the docs
and keep the current aliasing scheme.

Relates: #135552

Credit to @Wentao14614 for the initial observation.

[cla-checker-service]

💚 CLA has been signed

[github-actions]

🔍 Preview links for changed docs

• docs/reference/query-languages/esql/esql-time-spans.md

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[felixbarny]

Closing in favor of #136448

[bpintea]

@Zachary-hub thanks for your interest in contributing.
However, there have been some issues with the PR:

• the clarifications you wanted to add aren't correct: they reflect DATE_DIFF's unit argument format, not those of time spans; have a look at the docs of the function, specifically the paragraph following the table in "Datetime difference units" section.
• the fact that the space isn't relevant is documented already too.