[DOCS]: Add API reference links to longform Elasticsearch REST examples

[charlotte-hoblik]

This PR updates the docs to address missing links between longform REST API examples and the API docs.

Connected to: https://github.com/elastic/docs-content-internal/issues/441
Connected PR: elastic/elasticsearch-specification#5857

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/rest-apis/collapse-search-results.md
• docs/reference/elasticsearch/rest-apis/create-index-from-source.md
• docs/reference/elasticsearch/rest-apis/filter-search-results.md
• docs/reference/elasticsearch/rest-apis/highlighting.md
• docs/reference/elasticsearch/rest-apis/rescore-search-results.md
• docs/reference/elasticsearch/rest-apis/retrieve-inner-hits.md
• docs/reference/elasticsearch/rest-apis/search-suggesters.md
• docs/reference/elasticsearch/rest-apis/sort-search-results.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)