‼️ Require Read after Write: Let's have ZeBadge have status codes.

[mariobodemann]

Currently, most commands (except for the reading of settings / files) do not require any kind of response from the badge: ZeApp issues the command ("write image!") but we never know if it actually succeeds. (That's why the mass upload doesn't work: ZeBadge receives all images as one big blob. Instead it should receive one image after another, with a write of a status inbetween)

Please add the requirement that after every write from ZeApp to ZeBadge, a read needs to be happening.

This should be

a) ZeGood! if the command was executed successfully and no more information can be presented to ZeApp / ze caller.
b) ZeGood:123 if the command was executed successfully and needs to tell ZeBadge that 123 was the result. (aka, 123 pixels writen/ 123 loc achieved, etc.)
c) ZeBad! if an error occurred, but we can't know what specifically went wrong.
d) ZeBad:WORDS if an error with a message (WORDS, no newline) happend.

Please update all commands, and the documentation.