Improve QoS when GMS writes to MCL

[djordje-mijatovic]

GMS writes to a Kafka topic to report all data changes. The topic is treated as a change log but GMS is very optimistic when writing to it. We'd like a strong guarantee that any data change accepted by GMS will be written to Kafka.
There is currently a Callback mechanism in place but it is used only for logging purpose - we would like to extend mentioned Callback function to retry send operation for few time (configurable) and after few fails log the error as it is now.
Pay attention that failed on one topic should not have effect (slow down) on sending to other topics.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io