Investigate burst of invalid messages right at bootstrap time

[masih]

Immediately after bootstrap there seem to be a burst of invalid messages. Understand why; e.g. is there a timing issue where we may recieve QUALITY messages for an instance that we have not strated yet and drop them as invalid? In which case the very first bootstrap instance will suffer. Since those errors will prohibit propagation of QUALITY messages.

Grafana data to analyze: https://grafana.f3.eng.filoz.org/d/edsu1k5s7gtfkb/f3-passive-testing?orgId=1&from=1732801290780&to=1732802842780&var-network=mainnet&var-instance=ida.f3.eng.filoz.org:80

[masih]

Note that this is happening right at the very beginning, i.e. start of instance 0. Occurrences in successive instances is expected due to lingering non DECIDE messages from previous instance.

[masih]

Adjustments made in network 20, 21 and 22 seem to have removed the burst of invalid messages at initial instance. Screenshot below is from bootstrap of network 22 on mainnet:

We need to get to the bottom of it.