Bug: Selection inconsistency when table structure changes

[BUZZARDGTA]

Description:
When selecting cells in the table, if a row or column is added or removed nearby, the selection remains tied to the previous data instead of adjusting to reflect the updated table structure.

This leads to an inconsistent user experience, as the selected cells no longer represent the intended data.

Steps to Reproduce 1:

• Select a cell from one of the connected or disconnected tables.
• Wait for a player to add or remove a row or column near the selected cells.
• Observe that the selection remains tied to the previous positions instead of updating to match the new table layout.

Expected Behavior 1:
The selection should dynamically adjust to reflect the updated table structure, ensuring that the intended data remains selected.

Steps to Reproduce 2:

• Select the cell from a player connected.
• Wait for that player to disconnect.
• Observe that the selection remains tied to a new player from this same position.

Expected Behavior 2:
The selection should deselect this position, ensuring that the intended data remains unselected, or select the newly disconnected player at same position.

[BUZZARDGTA]

I currently have no plans to fix this issue, as I’m unsure how to address the bug or implement a solution.

[BUZZARDGTA]

Reopening because there's still an issue: when a player is removed from the connected table and added to the disconnected table, the selections in the disconnected table are not updated accordingly.

[BUZZARDGTA]

It’s likely the same issue with the connected table: if a player is added to the top of the table, the selections are shifted inconsistently.
Honnestly this part of the selection code is fucked up, I think I'll completely drop the algorythm implemented in this commit and instead add a memory for selections, when refreshing the gui it will select back if not selected each selections based on the IP address section.