[checkout] fix kafka restart

[puckpuck]

Changes

If Kafka is restarted, the checkout service will start to report very long response/acknowledgment times from Kafka. This may be due to the demo's unique configuration, which only has a single broker. To get around the issue, the Kafka/Sarama SDK is set to respond without full acknowledgments. This may lead to missed errors in certain situations but will allow the demo to recover from Kafka restarts and continue working without issues.

Part of this PR is to do proper handling of the Kafka message in a success or error scenario and also add attributes to the Kafka producer span related to details about the interaction with Kafka. A docs update will be required.

Merge Requirements

For new features contributions please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
  * [ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[puckpuck]

@julianocosta89 I moved to use semantic conventions or attribute names that align closer to what already exists. Let me know if we still need to update them.

[julianocosta89]

LGTM, thanks @puckpuck!