feat: add RecursiveSplitter component for Document preprocessing

[davidsbatista]

Related Issues

• fixes Add a Recursive Chunking strategy #8548

Proposed Changes:

• Adding a RecursiveSplitter, using a set of predefined separators to split text recursively - see issue for more details

How did you test it?

• local unit tests and integration tests plus CI tests

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: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 12712969950

Details

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

---

Files with Coverage Reduction	New Missed Lines	%
components/preprocessors/sentence_tokenizer.py	1	94.12%

Totals
Change from base Build 12710720579:	0.2%
Covered Lines:	8844
Relevant Lines:	9691

---

💛 - Coveralls

[davidsbatista]

@bglearning - mentioning you since I believe you were the one with most interest in this feature

[davidsbatista]

@sjrl I did the final fixes, so that special characters are also counted as a word unit - I've also requested a new review from you

[sjrl]

Looks great! Thanks for the work on this

[davidsbatista]

@sjrl thanks! this was a long, complex on - let's keep an eye on this, I suspect some edge cases might still show up.