[Request] Add warning against using ES|QL on production environments

[nastasha-solomon]

Fixes #4538

Previews: Updates the tech preview note to match the wording used in elastic/elasticsearch#103797

• Use ES|QL to investigate events
• Configure AI Assistant
• About detection rules
• Create an ES|QL rule
• Create rule

[github-actions]

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

• 🔨 Buildkite builds
• 📚 HTML diff: Buildkite - Jenkins
• 📙 Preview: Buildkite - Jenkins
• 🧪 Buildkite vs Jenkins diff

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[mergify]

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b issue-4538-update-esql-tp upstream/issue-4538-update-esql-tp
git merge upstream/main
git push upstream issue-4538-update-esql-tp

[nastasha-solomon]

Must've accidentally deleted some new content in the AI assistant topic, so am opening a fresh PR instead of reverting the conflict/change.