feat: Add DocumentWriter v2

[julian-risch]

Related Issues

• fixes DocumentWriter (v2) #5339

Proposed Changes:

This PR implements the new DocumentWriter component that can interact with all Stores and it adds two unit tests and one integration test.

How did you test it?

new unit tests, new integration test

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 5876944024

• 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.001%) to 48.131%

---

Files with Coverage Reduction	New Missed Lines	%
utils/context_matching.py	1	95.7%

Totals
Change from base Build 5867910704:	0.001%
Covered Lines:	11407
Relevant Lines:	23700

---

💛 - Coveralls

[silvanocerza]

I believe this test is not necessary as we're not even testing the DocumentWriter really.
If we want to test that the component does what we're supposed to do we just need to verify that self.store.write_documents is called when executing run.
The actual writing is not this component's responsibility.
Something like this should work.

@pytest.mark.unit
def test_document_writer_run():
    mock_store = store(MagicMock)()
    writer = DocumentWriter()
    writer.store = mock_store

    data = writer.input(documents=[Document(content="This is the text of a document.")])
    writer.run(data=data)

    assert mock_store.write_documents.called```