docs(influxql): restore ordering caution for FUTURE/PAST LIMIT on versions prior to v1.12.3

[Copilot]

PR #6872 corrected the FUTURE LIMIT/PAST LIMIT clause order in the docs to match the v1.12.3 fix, but left no warning for users still on older versions where the reversed order (PAST LIMIT before FUTURE LIMIT) is required.

Changes

• content/influxdb/v1/query_language/spec.md — Adds [!Caution] after the existing ordering [!Note] in both CREATE DATABASE and CREATE RETENTION POLICY grammar sections, directing users on pre-v1.12.3 to use the old order and linking to the v1.12.3 release notes.

• content/enterprise_influxdb/v1/query_language/spec.md — Same cautions, but without an upgrade suggestion since Enterprise v1.12.3 is not yet GA.

Each affected grammar block now reads:

> [!Note]
> When using both `FUTURE LIMIT` and `PAST LIMIT` clauses, `FUTURE LIMIT` must appear before `PAST LIMIT`.

> [!Caution]
> **Prior to InfluxDB v1.12.3**, when using both `FUTURE LIMIT` and `PAST LIMIT` clauses,
> `PAST LIMIT` must appear before `FUTURE LIMIT`.
> [Upgrade to InfluxDB v1.12.3 or later] to use the order shown above.

Original prompt

prior to #6872, we had a warning about the ordering of future and past limits in InfluxQL for v1. Restore it as a caution callout for users not yet on v1.12.3. The caution for Enterprise shouldn't suggest upgrading--the release isn't generally available yet.

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[jstirnaman]

I'll merge this into the v1.12.3 redo (delaying Ent publish until GA) and update it there.

[jstirnaman]

Closing — the caution notes were incorrect. The correct InfluxQL syntax has always been FUTURE LIMIT before PAST LIMIT. The v1.12.3 fix addresses Enterprise meta-node recording, not parser syntax order. See #6945 review comments.