[bug]: Capturing Multiple Stones in a chain

### Describe the bug

We only capture the "representative" stone for the chain when updating the board.


### Steps to reproduce

```rust
game.make_move(0, 0).unwrap();
game.make_move(0, 1).unwrap();
game.make_move(1, 0).unwrap();
game.make_move(2, 0).unwrap();
game.make_move(2, 2).unwrap(); // useless move to pass the turn
game.make_move(1, 1).unwrap(); // capture both "Black"(blue) stones
```

### Expected behavior

We expect the board representation to have empty positions of the board for each of the stones that are captured. Not just the one stone that is being used to represent the chain of stones.

### Additional information

_No response_

### Operating system

Linux

Start at the game.make_move calls in the reproduction sequence and run them to confirm that capturing a chain clears only its representative stone. Trace the board-update logic used by the final capture. Done means every captured stone position is empty, not only the position representing the chain.

Written by the indexing model from the issue text.