## Summary

Adds identity mappings for the five static section anchors defined in
`search-connection-details.md`. The page has a self-redirect for legacy
anchor aliases; without these mappings, cross-repository deep links to
its current anchors fail validation.

For example, [elastic/cli#624](elastic/cli#624)
links to the explicitly defined `find-endpoint-cloud-self-managed`
anchor:

```
docs-content://solutions/elasticsearch-solution-project/search-connection-details.md#find-endpoint-cloud-self-managed
```

Although that anchor exists in the current document, validation fails
because the self-redirect intercepts the link and its anchor map only
handles legacy aliases:

```
Redirect rule for 'solutions/elasticsearch-solution-project/search-connection-details.md' in 'docs-content' found, but top-level rule did not handle anchor '#find-endpoint-cloud-self-managed'.
```

This provides at least a temporary solution that keeps the current
document linkable through its explicitly defined section anchors while
preserving the legacy anchor redirects. The H1 anchor and generated
anchors are intentionally excluded.

## Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this
contribution?
- [x] Yes
- [ ] No

Tool(s) and model(s) used: Cursor with GPT-5.6 Sol. Used to inspect the
redirect behavior, verify every added anchor against the static anchors
in the source document, and prepare this focused change.

Co-authored-by: Cursor <cursoragent@cursor.com>