feat(kafka): add producer config capabilities for connections

[sicoyle]

Description

For the sidecars using the existing kafka client configurations, after a connection has been closed by the client after the default connection idle timeout of 9 minutes, then if that sidecar goes to write and publish a message they will see a write: broken pipe err. This is due to the connection being deemed idle, but the sidecar has no idea, and so when it tries to publish, then it is doing so to a closed connection to which we see that error. It is quite confusing for end users, and so these metadata fields allow us to keep a connection alive and establish a refresh for the topic metadata such that the connection may be kept alive indefinitely if desired.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[sicoyle]

I can update docs after I get initial feedback here pls :)

[sicoyle]

Looks like main still has rabbit mq issues based on these test results

[sicoyle]

unrelated failure due to stable components certification test for bindings.rabbitmq and pubsub.rabbitmq

[sicoyle]

ready!

[sicoyle]

this is now a dependency: dapr/kit#88

[olitomlinson]

I've had a couple of issues with broken pipe so this fix will be well received :)

[sicoyle]

ready

[sicoyle]

ping @ItalyPaleAle ready :)

[sicoyle]

ping for review please

[sicoyle]

ready for review please

[yaron2]

@sicoyle please see latest comments from @JoshVanL. We should be good to merge once addressed

[sicoyle]

addressed feedback. Thanks @JoshVanL

[sicoyle]

ready @ItalyPaleAle Thanks for the extra feedback!