feat: PyPDFToDocument - add new customization parameters

[anakin87]

Related Issues

• part of PyPDFToDocument: make conversion customization easier for users #8553

Proposed Changes:

• Add new initialization parameters to PyPDFToDocument to customize the text extraction process from PDF files.
• These parameter won't be used if a custom converter is provided (it will be deprecated in chore:PyPDFToDocument - deprecate converter init parameter #8569)

How did you test it?

CI, new test

Notes for the reviewer

I don't particularly like the addition of all of these new init parameters, but we have already discussed and discarded the idea of having a single extraction_kwargs dict.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 12033758738

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 90.349%

---

Files with Coverage Reduction	New Missed Lines	%
components/converters/pypdf.py	6	93.18%

Totals
Change from base Build 12031967571:	0.03%
Covered Lines:	8014
Relevant Lines:	8870

---

💛 - Coveralls

[vblagoje]

Seems fine only minor nitpicking comments.
Maintaining compatibility on this one is going to be hard with so many fields. Any other way to deal with these in less breaking manner? Perhaps some config dictionary or something....

[anakin87]

Perhaps some config dictionary or something....

This was my original idea but then we discarded it to keep more control on accepted parameters and serialization.