Some Watermill internal tests are written with null payloads

[dkotik]

https://github.com/ThreeDotsLabs/watermill-sql/blob/master/pkg/sql/pubsub_test.go#L466 has null payloads:

messagesToPublish := []*message.Message{
	message.NewMessage("0", nil),
	message.NewMessage("1", nil),
	message.NewMessage("2", nil),
}

The acceptance tests never run a scenario with a NULL payload. Using that test sample caused SQLite driver tests to fail.

Currently, I filled in the samples with some data for testing. But this left me with a question: are empty payloads for messages correct behavior?

I believe the answer to this question should be "no" and that the answer must be codified in the official implementation tests.

[roblaszczak]

Hey, for the rest of the Pub/Subs it will work, but I won't expect to have null back when subscribing. In other words, I would allow null, but in response it can be []byte{}

[dkotik]

Added an appropriate test, satisfied it, and added notes pointing to this issue: ThreeDotsLabs/watermill-sqlite@624a410

[dkotik]

Should I move this test into all the official tests for all pubsubs? @roblaszczak if so, please assign this issue to me