Support a "bomb-pot" button

[ctm]

Make it so mb2 can use a separate button to keep track of who acts last (and hence, who acts first) for bomb pots.

• [x] Add a Option<SeatIndex> alt_button field to Table
• [x] Add a bool use_alt_button to Options
• [x] Add a use_alt_button() method to GameInfoBuilder<HoldEm> and GameInfoBuilder`
• [x] Add a use_alt_button() method to GameGroup
• [x] Update wsop_2024_41_nlhe_plo_with_double_board_bomb_pot to add alt_button() where needed
• [x] Add to TableStatus
  • [x] A bool use_alt_button
  • [x] An Option<SeatIndex> alt_button
• [x] Replace all instances of Table::button with &self.button
• [x] Replace all instances of .button.seat with button_seat()
• [x] Update Table::button_seat to use self.game.use_alt_button()
• [x] Update all assignments to button.seat
• [x] Update Table::advance_button to use the above
• [x] Scrutinize any remaining code that uses Table's button field
  • [x] See if it should be using button_seat
  • [x] See if it needs to know about any of the above
• [x] Add sanity checks to make sure we're not using the alt-button with blinds
• [x] Test all the above
• [x] Update the client
  • [x] Have it capture the new TableStatus fields
  • [x] Have it display a dimmed button in back of the regular button if alt_button is Some
• [x] Profit! Test some more

[ctm]

Yesterday, I created this issue with a few ideas and questions, but after sleeping on it, I decided to go with a very simple Options based solution. For posterity, here is what I initially had in this issue description:

This should not actually include any bomb-pot specific code; it does, however, need to support the functionality that is currently missing from the new Double Board Bomb Pot structure (#1348). I don't want to add all-singing, all-dancing support for an arbitrary number of buttons, but if I can avoid painting myself into a corner, I'd like to.

So, I need to quickly see if I can find the various structures that have called for multiple buttons in the past. I think at least one iteration of CHORSE did. There may be others. I may as well ask on the BARGE list after I do a small amount of research myself.

Off the top of my head, I can think of a few different ways to add this functionality, one would be to add more state to Options, another would be to make a struct that implements GameGroup, but has the special property of only manipulating state and never have a hand dealt. Either way, I then need to figure out do I want a set of pseudo-commands that are fairly fine-grained but would give us a lot of flexibility (includeing—probably—the ability to combine them errantly), or do I want something that is more akin to "just use (for some definitions of use) an alternate button here".

We're still three months away from June 15th, but since testing will initially only be done when someone chooses "WSOP 2024\-style #41 NLHE & PLO with Double Board Bomb Pots, adding the functionality sooner, rather than later may be less stressful.

[ctm]

Although I don't yet have the client showing the alternate button, I do—in theory—have all the server code in place. Light testing hasn't revealed any bugs, so it's time for me to update the client and then test some more.

[ctm]

Done. Deploying now. However, I changed TableStatus more than I expected to.