FYI ag grid and VISIBLE selected vs (just) selected

[series0]

Not really a justpy issue, but use of that example could be slightly confusing.

In the ag-Grid Guide, Grid Events, Example 3 there is an issue with deselection events.

Since the index returned from the grid is really NOT an index, but, a visible index (rowIndex), the example can get lost when there are invisible selected rows.

To see the issue:

1. select Toyota
2. Use the ag filter on Make and type in 'Ford'
3. With only the Ford row visible select it
   So far so good
4. Deselect Ford
   See that the wrong row is removed.

The removal code much match the incoming deselection event row with the selected_rows data. The index is unreliable.
{I suppose since there is no unique guarantee on the index, the entire data row should be matched, but some grids might have multiple matching rows (all the data).} Granted this is a fringe case and inadvisable in terms of setup, but it is possible, clearly.

Interaction between ag-Grid and anything, justpy in this case, has to account for the oddity of (visible) rowIndex versus (actual) selected row index.