util: test_timeline forcejump should not show "missed" syncs

[valarnin]

One problem with forcejump, and this is maybe more of a problem for the test_timeline is that the test_timeline output will then show a massive amount of false positive missed syncs:

Probably not in this example, but when I wrote the Forked Tower / OC timelines the other issue comes about if the forcejump location also has a branch near and those branches contain a forcejump which then causes wrong output to be displayed.

Originally posted by @Legends0 in #936 (comment)

[xiashtra]

Part of the problem here seems to be using a jump with a forcejump at the exact same time to force the timeline into one of two possible branches. I only use forcejump when it is part of a single path, such as returning to the main timeline after a branch. For example:

start
possible jump to block 1
possible jump to block 2
block 1 with forcejump to block 3
block 2 with forcejump to block 3
block 3

I'm not sure the jump with immediate forcejump to force the timeline into one of two branches is an intended use case. In fact, it could cause the timeline to go down the r11s-scythe-1-crush-1 branch even when it shouldn't. In the case of a slightly delayed B414 line, the forcejump would be hit before the jump window has a chance to sync and jump to the r11s-scythe-1-comet-1 branch. I'd go so far as to say having a jump and forcejump with the exact same time should be a lint error.

[Legends0]

It happens when the forcejump sync is missed too.

The log here had 917.3 where the startsUsing happened.