[#1296] Document LDIF backend configuration and proxy suffix limitations (#1298)
## Summary
Add the missing administration-guide procedure for configuring and
operating the built-in LDIF backend. The chapter covers its in-memory
reads and file rewrites, single base DN, backing-file path, enablement,
write policy, and limited custom-control support. It includes a minimal
LDIF file, `dsconfig create-backend --type ldif`, verification steps,
and a safe procedure for editing and reloading static data.
Explain how a local LDIF parent suffix coexists with subordinate proxy
backends. A subtree search that reaches an unavailable child route still
returns `UNAVAILABLE (52)`, even when some entries have already been
returned or the LDIF file contains copies of child base entries. The
chapter makes the boundaries of runtime fallback, result reconciliation,
and federation explicit.
## Validation
- Documentation unit suite: 26 tests passed; Antora page-title suite: 10
tests passed, with no failures, errors, or skips.
- AsciiDoc attribute check and cross-guide check: 604 file references
across 74 pages.
- Administration Guide PDF and Antora generation passed.
- Isolated-server smoke test passed for the documented create/get
commands, both sample entries, disabled/enabled LDAP writes, file
persistence, and disable/edit/enable reload. The temporary server was
stopped afterward.
- `git diff --check` passed.
Fixes #1296
Related to #1292 and discussion #554.