raidboss: timeline lint/test error message for use of forecejump on multiple lines instead of jump

[Legends0]

Feature(s) Requested

Just a thought I had while working on some timeline branches.
Two lines in a row with uncommented forcejump should result in a test or lint failure since this would indicate unreachable code exists in the timeline. A forcejump would skip over the subsequent forcejump line regardless of sync.

In my situation the correction was to use jump instead for the first forcejump, and then next either jump or forcejump could be used to skip over the lookahead:

Example:

50496.3 "--sync--" StartsUsing { id: "7602", source: "Marble Dragon" } forcejumo "oc-md-p2o"
50496.3 "--sync--" StartsUsing { id: "7614", source: "Marble Dragon" } forcejump "oc-md-p2+"
50497.3 "Imitation Blizzard (circles/crosses?)" #Ability { id: "7602", source: "Marble Dragon" }

Should warn/error for this as. Hinting for use of jump is an added bonus:

For instance:
Warning: Use of forcejump on multiple lines in a row leads to unreachable code, use jump instead:

50496.3 "--sync--" StartsUsing { id: "7602", source: "Marble Dragon" } jump 50795.7
50496.3 "--sync--" StartsUsing { id: "7614", source: "Marble Dragon" } forcejump "oc-md-p2+"
50497.3 "Imitation Blizzard (circles/crosses?)" #Ability { id: "7602", source: "Marble Dragon" }

[Legends0]

I suppose if it's wanted to actually sync to one of the two lines before the time happens that would be an exception. I'm unsure if we have a current use case for that.

Use like this would possibly make the timeline output look wrong since the output would use the first forcejump as a preview. So I think in that case a jump is actually preferred as it can have the lookahead lines manually created properly.