Results entry checks feature parity

[dunkOnIT]

Currently not doing WR warnings as we don't have records set up at all.

• MBLD time/cube warning
• Best single/worst single warning
• Time limit (per solve)
• Cutoff (cumulative time per solves)
  • Warn if doesn't meet
  • "Apply" cutoff - presumably by DNSing solves?
• DNS followed by valid result

[dunkOnIT]

@FinnIckler see the following fixes:

• "big difference between best and worst single" warning currently invokes if there is a DNF present - it shouldn't trigger for DNF or DNS
• Applying cumulative time limit: It automatically changes a result to DNF the first time a result is entered that exceeds the cumulative time limit - but if that DNF is replaced by another result, which also exceeds the cutoff, it doesn't (visually) change the result to DNF. It does submit a DNF result, though.
• If the non-last solve doesn't meet the cumulative time limit, it should be changed to DNF, and all subsequent solves not yet entered should be auto-populated as DNS (skimming the WCA Live code it looks like it does this - but if not let me know and I'll split this out into a lower-priority issue)

[FinnIckler]

For (2) can you give me an exact sequence of things I have to enter for this to trigger? I don't really get it

[dunkOnIT]

• First attempt: Enter a time that is just under the cumulative time limit
• Second attempt: Enter a time that will exceed the time limit
• Press tab to advance to the next scoretaking field - the second attempt will change to DNF
• Go back to the field where the DNF is entered: Change it to a time that will exceed the time limit
• Press tab: The time will not change to DNF as it should