This connects us to the header tip signal so that we can handle when the node is in pre & or headers sync. This calculates the progress of the pre or headers sync and adds it to our verification progress. Pre and headers sync take up 1% of verification progress each, then IBD begins at 2% progress as displayed on the block clock.
fix verification progress update math so that it doesn't go to 102 (verification progress + header progress) and now finishes at 100
Change how we consider to be synced within the block clock's perspective from a check on if verificationProgress is large enough to a query on the node to see if it is in ibd or not. This fixes the issue described here. The issue there is that we'd get some header and that would create a certain progress, and because the check for synced was that verification progress needs to be higher than 99, the UI would get stuck in a weird spot.
This connects us to the header tip signal so that we can handle when the node is in pre & or headers sync. This calculates the progress of the pre or headers sync and adds it to our verification progress. Pre and headers sync take up 1% of verification progress each, then IBD begins at 2% progress as displayed on the block clock.