refactor(engine): merge two legacy interfaces together

[pihme]

Description

• LegacyTypedStreamWriter already extended LegacyTypedCommandWriter
• This PR replaces all references to LegacyTypedCommandWriter with LegacyTypedStreamWriter
• It then merges the two interfaces and deleted LegacyTypedCommandWriter
• The net effect of this, is that we only need to replace one interface going forward

Related issues

relates to #9724

Definition of Done

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

   768 files   -   75     768 suites   - 75   24m 28s ⏱️ - 1h 15m 48s
6 032 tests  - 367  6 021 ✔️  - 367  11 💤 ±0  0 ❌ ±0 
6 216 runs   - 367  6 205 ✔️  - 367  11 💤 ±0  0 ❌ ±0 

Results for commit c4abc4e. ± Comparison against base commit 661e6bb.

♻️ This comment has been updated with latest results.

[Zelldon]

Just so I get it right. The idea is that we then in the end just replace the Writer interface with the new Builder interface to create the result, correct? :)

If this is the case makes sense to me.

[pihme]

@Zelldon please have another look. I rebased everything and reduced the one legacy interface.

Now, the next step will be to replace usages of this one legacy interface with new tasks - scheduled via ProcessingScheduleService. This task will probably get an object similar to the response builder at runtime. I say similar, because I do want to define a reduced builder (i.e. result has only records, no side effects, no response)

Details still need to be figured out, but this is the general gist of it.

[Zelldon]

Thanks 👍

[pihme]

bors merge

[zeebe-bors-camunda]

Build succeeded:

• Test summary
• Go linting
• Java checks