Move TypedRecord to api

[pihme]

Description

Moves TypedRecord to api package

Related issues

related to #9725

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]

Unit Test Results

   789 files  ±  0     789 suites  ±0   1h 42m 4s ⏱️ + 2m 26s
6 133 tests +97  6 126 ✔️ +97  7 💤 ±0  0 ❌ ±0 
6 302 runs  +97  6 295 ✔️ +97  7 💤 ±0  0 ❌ ±0 

Results for commit a3b3340. ± Comparison against base commit b4122ff.

♻️ This comment has been updated with latest results.

[npepinpe]

👍

• 💭 Out of scope, but I wonder why we override getKey() and getValue() in TypedRecord? 🤷

[pihme]

bors merge

[zeebe-bors-camunda]

Build succeeded:

• Test summary
• Java checks
• Go linting