feat: Add `min_top_k` to TopPSampler

[sjrl]

Related Issues

• fixes #issue-number

Proposed Changes:

This adds the parameter min_top_k to the TopPSampler which sets the minimum number of documents to be returned when the top-p sampling algorithm results in fewer documents being selected. The documents with the next highest scores are added to the selection.

This is useful when we want to guarantee a set number of documents will always be passed on, but allow the Top-P algorithm to still determine if more documents should be sent based on document score.

Also some minor refactoring was done. The biggest change/addition was changing ComponentErrors to logger.warning messages to allow the component to still run even when running into small edge cases.

How did you test it?

Expanded tests

Notes for the reviewer

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 10485448854

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.06%) to 90.189%

---

Totals
Change from base Build 10419214121:	0.06%
Covered Lines:	6959
Relevant Lines:	7716

---

💛 - Coveralls

[anakin87]

@sjrl I have pushed a small change to fix typing issues. Please take a look and confirm it is ok. Let's wait for the docstrings review...

[sjrl]

@sjrl I have pushed a small change to fix typing issues. Please take a look and confirm it is ok. Let's wait for the docstrings review...

Thanks! Looks good, I only made one small change to the docstring