[8.x](backport #4686) o11y AI assistant: add doc entry about the product doc

[mergify]

Description

Add documentation entry about for Elastic product documentation feature for the o11y AI Assistant, and add link for air-gapped installation (for stateful only)

Documentation sets edited in this PR

• Stateful (docs/en/observability/*)
• Serverless (docs/en/serverless/*)
• Integrations Developer Guide (docs/en/integrations/*)
• None of the above

Related issue

Part of elastic/kibana#199999

Checklist

• Product/Engineering Review
• Writer Review

Follow-up tasks

• This PR does not need to be ported to another doc set because:
  • The concepts in this PR only apply to one doc set (serverless or stateful)
  • The PR contains edits to both doc sets (serverless and stateful)
• This PR needs to be ported to another doc set:
  • Port to stateful docs: <link to PR or tracking issue>
  • Port to serverless docs: <link to PR or tracking issue>

---

This is an automatic backport of pull request #4686 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 5b4a5e2 has failed:

On branch mergify/bp/8.x/pr-4686
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 5b4a5e2b.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/en/observability/observability-ai-assistant.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/en/serverless/ai-assistant/ai-assistant.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

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.}