Prevent duplicate slot / shred ever being published

We need a durable slot / leader store variable to ensure that when the validator is restarted, we don't publish in the same leader slot as we have before.

We also potentially need to survive a reboot. In that case, we could just wait 32 slots after a fresh reboot to ensure we haven't published, or use a file to save state.