feat: add Presidio integration for PII detection and anonymization

[SyedShahmeerAli12]

Closes #3063

What this adds

Three new Haystack components using Microsoft Presidio:

• PresidioDocumentCleaner — anonymizes PII in list[Document], returns new Documents without mutating inputs
• PresidioTextCleaner — anonymizes PII in list[str], useful for sanitizing user queries before LLM calls
• PresidioEntityExtractor — detects PII entities and stores them in Document metadata under the "entities" key

Usage example

from haystack_integrations.components.preprocessors.presidio import PresidioDocumentCleaner
from haystack import Document

cleaner = PresidioDocumentCleaner()

result = cleaner.run(
    documents=[Document(content="My name is shahhmeer, email: ashahmeer73@gmail.com")]
)

# → "My name is <PERSON>, email: <EMAIL_ADDRESS>"

[sjrl]

@SyedShahmeerAli12 thanks for contributing! Please read the contribution guidelines here https://github.com/deepset-ai/haystack-core-integrations/blob/main/CONTRIBUTING.md#create-a-new-integration and run the scaffolding script to help fill in some missing aspects of your contribution.

Also make sure to run the linter and the tests

[SyedShahmeerAli12]

▎ Hello @sjrl I've implemented all three components proposed in this issue:

PresidioDocumentCleaner : anonymizes PII in list[Document]
PresidioTextCleaner : anonymizes PII in list[str] for query sanitization
PresidioEntityExtractor : detects PII entities and stores them in Document metadata

All CI checks are passing. Happy to make any changes based on your feedback

[sjrl]

@SyedShahmeerAli12 a few more high-level comments before I do an indepth review:

• Please add a new entry in .github/labeler.yml
• We recently add code coverage support so please add a new entry in .github/workflows/CI_coverage_comment.yml
• Add the new integration to the table in the root README.md https://github.com/deepset-ai/haystack-core-integrations/blob/main/README.md

[SyedShahmeerAli12]

Addressed all comments removed the ## Contributing header from README to match the pgvector format, fixed alphabetical ordering in both the root README table and CI_coverage_comment.yml. Python 3.14 was already in place.

[SyedShahmeerAli12]

• warm_up() — AnalyzerEngine/AnonymizerEngine do load spaCy ML models, so moved engine init into warm_up()
  across all three components. Updated integration tests accordingly.
• Keyword-only args — Added *, to all three init methods.
• Return types — Replaced dict[str, Any] with proper typed returns, removed unused Any import.
• dataclasses.replace() — Used in PresidioEntityExtractor instead of constructing a new Document.
• Doc links — Added https://microsoft.github.io/presidio/supported_languages/,
  https://microsoft.github.io/presidio/supported_entities/, and https://microsoft.github.io/presidio/analyzer/
  links to docstrings in all three components.

[SyedShahmeerAli12]

Thanks @sjrl Addressed all four points:

• Broken doc link — Fixed supported_languages/ → analyzer/languages/
• warm_up() guard — Added _is_warmed_up flag; repeated calls return early
• Auto-warm on run() — Replaced RuntimeError with lazy warm_up() call on first run()
• Docstrings — Updated to reflect lazy loading behaviour
• Tests — Added _make_*_with_mocks() helper to prevent auto-warm from overwriting injected mocks

[SyedShahmeerAli12]

Hi @sjrl, addressed all three comments:

• presidio.yml — Regenerated from the template (compute-test-matrix job, pinned action versions, push trigger, coverage steps, integration-cov-append-retry). Also added integration-cov-append-retry script to pyproject.toml.
• presidio_document_cleaner.py — Removed cleaned.append(doc) so documents that fail anonymization are dropped entirely rather than passed through unanonymized.
• presidio_entity_extractor.py — Updated warning message to "Skipping extraction, keeping document" to accurately reflect the behaviour.
• Test — Updated test_run_skips_on_error in the cleaner tests to assert len(result["documents"]) == 0.

[sjrl]

Thanks @SyedShahmeerAli12 ! Almost there, could you look at the failing CI check here

[SyedShahmeerAli12]

@sjrl all checks are passing now. Ready for another review when you get a chance!

[sjrl]

Thanks for the contribution!