Handle orphaned execution payloads

We need to make sure to properly handle orphaned execution payloads. There are two places I can think of right now:
- range sync when we fetch block/envelopes by range, we need to skip trying to sync those even if a peer serves them and downscore the peer
- archiving of finalized data, we need to avoid storing them in archive db, can have a separate storage for orphaned execution payloads, we have the same for blocks

We need to check with the beacon block if it's building on full or empty. The parent hash in the bid from block N is equal to the block hash in the bid of N-1? If yes it's full and the Payload of N-1 is included. If it's not then empty and the Payload is orphaned.