Remove legacy writers

[Zelldon]

Description

Removes the usage of the old LegacyWriter interface and implementation. Furthermore, it removes the need of the TypedStreamWriterFactor from the Context and tests.

The StreamProcessorHealthTests have been rewritten to use the new extension and mocked record processor. It felt much easier to write such test I have to say.

Related issues

closes #9724

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

• The changes are backwards compatibility with previous versions
• If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

• There are unit/integration tests that verify all acceptance criterias of the issue
• New tests are written to ensure backwards compatibility with further versions
• The behavior is tested manually
• The change has been verified by a QA run
• The impact of the changes is verified by a benchmark

Documentation:

• The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
• New content is added to the release announcement
• If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

[github-actions]

Test Results

   852 files  ±    0     852 suites  ±0   1h 39m 12s ⏱️ + 1m 15s
6 272 tests +116  6 262 ✔️ +117  10 💤  - 1  0 ❌ ±0 
6 456 runs  +116  6 446 ✔️ +117  10 💤  - 1  0 ❌ ±0 

Results for commit 1deecf3. ± Comparison against base commit a66af76.

[deepthidevaki]

🚀

bors r+

[zeebe-bors-camunda]

Build succeeded:

• Go linting
• Test summary
• Java checks