feat: Add support for message keys in typed producer

[rohits1101]

Pull Request Submission Checklist

Please confirm that you have done the following before requesting reviews:

• I have confirmed that the PR type is appropriate for the change I am making according to
  the Honest Pull Request and Commit Message Naming Conventions.
• I have typed an adequate description that explains why I am making this change.
• I have installed and run standard pre-commit hooks that lints and validates my code.

Description

• The kafka producer API does not support setting message keys
• In our kafka-infrastructure, by default the topics are set to compat on keys
• Having empty keys deletes the messages on the topic
• To solve this, we need to do one of the two:
  1. Change the topic compaction policy (to not delete, to not compact on message keys)
  2. Change the KP interface to produce the messages with keys
• We can go ahead with (2) because it also aligns with the organization wide convention of (1) topic deletion policy, (2) messages between acq, and mlops having their keys as application-status-ids

AC

• Update the producer interface to also accept the keys, and produce the messages with message keys

---

This change is 

[misranitin]

If the default value of msg.Key is nil, then can we skip checking if key is nil?

[rohits1101]

Checked, the default is indeed a nil. Pushed a fix to assign the key directly.

[onkarbanerjee]

This file is supposed to be synced from .github as mentioned in the comment above. Can we follow the same?

[onkarbanerjee]

Not sure, why this file is not synced from .github though

[rohits1101]

Looks like we are performing these extra steps specific to KP. To sync them from workflows, we'd have to copy over these to that repo, and sync from there. Doing that for a single repository doesn't seem worth the effort.

[onkarbanerjee]

In general i feel this file can very much be synced from .github and maybe use one of the existing ones. If we feel like we need separate steps for integration tests then we can use a build file without the int tests from .github and a custom integration_tests.yaml file.

[rohits1101]

I've created a linear ticket for this https://linear.app/honestbank/issue/NERDS-236/sync-kp-workflows-from-the-shared-workflows

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[cyberhck]

keys aren't supported in typed producer by design, they're supposed to be done through middlewares (they're work in progress in #82 ) please make that ready instead.