Implement a confirmation dialog or "Dead tossup" button to prevent accidentally pressing "Next" twice

[hftf]

Since the throw-out/replacement flow is flawed (#212 #245 etc.), add a barrier to preemptively prevent situations that require manually editing prior game state.

[alopezlago]

I'm leaning towards marking this as won't fix. For low-scoring games this becomes a hindrance, and I'm not aware of having to throw out questions because tossups were read in the wrong order (though I could be mistaken). The button could be disabled for a short amount of time (250 ms maybe), but that seems like overkill.

[hftf]

I think changing the text of the button to "Next (dead tossup)" or something would be a simple improvement.

[alopezlago]

Should it show the label if the tossup has negs but is still dead, or if there's only no buzzes?

[alopezlago]

It's a bit unbalanced if "(dead)" is added to the text. "(dead)" has the issue of being less useful if there were negs in the tossup, since it doesn't prevent this accidental case. Other forms like "(unanswered)" are much bulkier though.