disable buttons and checkboxes in the click handler

[ctm]

Find the various places where mb2 accepts clicks and make sure that in the click handler itself, the button is disabled.

This is a fix on the client side for the problem I just fixed on the server side (#1166). In theory, since it's fixed on the server side, the particular behavior we saw won't happen, but it should be fixed in both places, especially since there still could be weirdness in the UI.

[ctm]

I removed the high priority label, because I don't see this causing trouble, and I have a lot more important things to do right now.

[ctm]

BTW, there's a chance that doing this naively will actually have an embarrassing downside, so it's best to only work on this when I can start running tests on devctm.com again. IOW, I absolutely shouldn't do this during the WSOPS Series on craftpoker.com.

[ctm]

Not doing this makes it impossible for people to know that their click was seen if they're lagged. LLew, for example, said in chat:

whats going on? i had to check like 5 times!

and looking at the logs I see:

mb2=> select id, hand_id, received_at at time zone 'america/denver', message from private_table_messages where player_id = 23 and table_id = 5179 order by received_at;
[...]
 11431912 |  350781 | 2023-06-14 18:31:19.287043 | "AdvancedActionCleared"
 11431913 |  350781 | 2023-06-14 18:31:33.892105 | "AdvancedActionCleared"
 11431915 |  350781 | 2023-06-14 18:31:33.897036 | {"ActionSet": "Check"}
 11431916 |  350781 | 2023-06-14 18:31:33.897041 | {"ActionSet": "Check"}
 11431917 |  350781 | 2023-06-14 18:31:33.897042 | {"ActionSet": "Check"}
 11431918 |  350781 | 2023-06-14 18:31:33.897043 | {"ActionSet": "Check"}
 11431935 |  350781 | 2023-06-14 18:31:57.382103 | {"CantCheck": 1500}

which basically means she was clicking on the advanced action check box, not getting any feedback and then clicking again.

That is extremely unfair to anyone and would put someone off the interface, whereas if we were to disable the checkbox on the first click, we could at least document what is going on until we do a little further and actually put lag detection into the client (#160).

So, I've added the high priority label back in.

[ctm]

BTW, disabling a button makes sense, but disabling check-boxes is probably not what we want to do, because someone can change their mind during the lag. It makes more sense to tentatively update the check-box with the value desired, but to change it to gray and add a tooltip that succinctly explains that the message has been sent, but not yet acknowledged. Unfortunately, that requires more coding than merely disabling.

[ctm]

In light of the above comment, this issue is really not easy and since it's not easy, and since we need a more encompassing lag reporting system, I'm stripping it of both easy and high priority.