KMS gets stuck in a retry loop when reading a null key from Kafka #80
Description
Have observed a scenario where the KMS was stuck in a retry loop, scheduling actor not able to respond to any messages. Turned out to be because null keys were being sent to the schedule topic. We should handle this in the decoder, returning a decoding error if the key is null.