Allow columnVisibility logic inversion so only true columns are visible

[marcebdev]

Pretty simple, I have list of checkbox (could be a multi select) or whatever else you want to select which columns are visible.

The way it's setup outside of pretty simple use cases feels like it quickly becomes unintuitive or more complicated than it has to. I'd also argue as a table gets larget the amount of hidden (optional) columns exceeds the number of visible, so it's easier to mark 10 as visible than it is to mark 20 as invisible, though that's mostly boilerplate

The paths forward become:

1. write out the full list of columns into the state (to explicitly track both true & false)
2. invert the state of everything so you only care about the false columns, checkboxes aren't checked based on true, but based on wether a column is not marked as false. Basically it becomes hidden state instead of visible state

Feels like allowing inverting couldn't hurt but it would be much more intuitive, especially for linking to external interactions in many cases. It's fairly surprising that this isn't an option and the state functions "backwards".