Exporter sometimes misses sequence number zero

[amirylm]

Describe the bug

In case the exporter got the first two (or more) decided messages via network publish rather than via sync protocol, the message with sequence number 0 won't be saved.

A sync in a later phase won't help as it will start from the highest known sequence which is probably not 0..

To Reproduce

Expected behavior

Screenshots

Node (please complete the following information):

• Operator Version: >v0.1.5

Additional context

The issue is coming from this check:

https://github.com/bloxapp/ssv/blob/e4ae575fb724cac826e780fcac1c51222ff70241/exporter/ibft/decided_reader.go#L127

While sync is using latest decided (which is not 0):

https://github.com/bloxapp/ssv/blob/e4ae575fb724cac826e780fcac1c51222ff70241/ibft/sync/history/history.go#L59