[8.16] [ESS][Serverless] Updates nav references for Cloud Security and AI sections (backport #6147)

[mergify]

Fixes #6140. Part of #5896.

Updates how we tell readers to find pages within Kibana. Affects pages in the Cloud Security and AI for Security sections.

Minor changes throughout, refer to the diff. Made a few small opportunistic fixes but almost all the changes are just to navigation language.

All ESS pages that were updated have corresponding serverless page updates. The reason for there being an odd number of files changed is due to the use of an include for one of the pages, so changing one page affected two pages. Thanks!

---

This is an automatic backport of pull request #6147 done by Mergify.

[mergify]

Cherry-pick of 3c3e4c8 has failed:

On branch mergify/bp/8.16/pr-6147
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit 3c3e4c82.
  (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/AI-for-security/connect-to-azure-openai.asciidoc
	modified:   docs/AI-for-security/connect-to-bedrock.asciidoc
	modified:   docs/AI-for-security/connect-to-byo.asciidoc
	modified:   docs/AI-for-security/connect-to-openai.asciidoc
	modified:   docs/AI-for-security/connect-to-vertex.asciidoc
	modified:   docs/cloud-native-security/cspm-benchmark-rules.asciidoc
	modified:   docs/cloud-native-security/cspm-get-started-aws.asciidoc
	modified:   docs/cloud-native-security/cspm-get-started-azure.asciidoc
	modified:   docs/cloud-native-security/cspm-get-started-gcp.asciidoc
	modified:   docs/cloud-native-security/d4c-get-started.asciidoc
	modified:   docs/cloud-native-security/environment-variable-capture.asciidoc
	modified:   docs/cloud-native-security/kspm-benchmark-rules.asciidoc
	modified:   docs/cloud-native-security/kspm-get-started.asciidoc
	modified:   docs/cloud-native-security/kspm.asciidoc
	modified:   docs/cloud-native-security/security-posture-management.asciidoc
	modified:   docs/cloud-native-security/vuln-management-get-started.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/AI-for-security/connect-to-azure-openai.asciidoc
	deleted by us:   docs/serverless/AI-for-security/connect-to-bedrock.asciidoc
	deleted by us:   docs/serverless/AI-for-security/connect-to-byo-llm.asciidoc
	deleted by us:   docs/serverless/AI-for-security/connect-to-openai.asciidoc
	deleted by us:   docs/serverless/AI-for-security/connect-to-vertex.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/benchmark-rules.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/cspm-get-started-azure.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/cspm-get-started-gcp.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/cspm-get-started.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/d4c-get-started.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/environment-variable-capture.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/get-started-with-kspm.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/kspm.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/security-posture-management.asciidoc
	deleted by us:   docs/serverless/cloud-native-security/vuln-management-get-started.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.}