docs: add quality and throughput tuning guide

[binaryaaron]

Summary

• add a quality-first guide for tuning Anonymizer
• define quality gates, configuration freeze points, and representative benchmark design
• document controlled throughput experiments and deployment-specific options
• link the guide from the documentation navigation and troubleshooting workflow

Issue

No linked issue is needed for this maintainer-owned documentation improvement.

Validation

• make docs-build
• make format-check
• make copyright-check
• independent council review against the current implementation and public documentation

Public API and data safety

No public API or default behavior changes. Examples use generic placeholder data and contain no credentials or real PII.

[greptile-apps]

Confidence Score: 5/5

The documentation-only PR appears safe to merge.

Summary

• Defines quality gates, configuration freeze points, and representative benchmarks.
• Describes controlled throughput experiments and deployment-specific controls.
• Links the guide from troubleshooting and the MkDocs navigation.
• Clarifies that Rewrite latent-entity detection is not constrained by the standard entity_labels allowlist.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Define quality gate] --> B[Establish quality configuration]
    B --> C[Freeze configuration]
    C --> D[Design representative benchmark]
    D --> E[Tune one throughput layer]
    E --> F{Quality and stability pass?}
    F -->|No| E
    F -->|Yes| G[Select smallest stable production setting]

Loading

[alexahaushalter]

Shall we suggest a range to vary it within? Could also add another column to this table with suggested values to check between or suggested values for what a "gradual" increase means for that variable