feat: allow DocumentJoiner to accept top_k parameter in run method

[Varun-Krishnan1]

Related Issues

• fixes DocumentJoiner component's run method doesn't accept a top_k value #7702

Proposed Changes:

The issue was caused by the DocumentJoiner component's run method not accepting the top_k parameter. This resulted in a ValueError when trying to pass top_k at query time using pipe.run("DocumentJoiner": {"top_k": top_k}).

To solve this issue, I updated the run method to accept the top_k parameter and use it to limit the number of returned documents. The relevant lines in the run method were modified to check for the top_k parameter and apply it accordingly.

How did you test it?

I added a unit test to the test_document_joiner.py file to ensure the top_k parameter works correctly when provided in the run method. The test verifies that the run method limits the number of returned documents to the specified top_k value.

Notes for the reviewer

None

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
• I have added a release note file using reno

[CLAassistant]

All committers have signed the CLA.

[coveralls]

Pull Request Test Coverage Report for Build 9120287116

Details

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

---

Totals
Change from base Build 9116506765:	0.002%
Covered Lines:	6594
Relevant Lines:	7279

---

💛 - Coveralls

[silvanocerza]

Nice, thanks!