Optimize column state sync

[haynesjm42]

Partial fix for #3903

Hoist P/R Checklist

Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

• Caught up with develop branch as of last change.
• Added CHANGELOG entry, or determined not required.
• Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
• Updated doc comments / prop-types, or determined not required.
• Reviewed and tested on Mobile, or determined not required.
• Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

[amcclain]

This looks like a great simplification and clean-up - and now I see why we saw performance worsen in proportion to number of columns being shown/hidden!

Eager to take it - just now wondering if it requires update to AG v32....

[amcclain]

Does this case risk spoiling the change detection below due to unfortunate hide/hidden mismatch?

I know it's an edge-case where we have this auto-column inserted by the grid - it's due to direct use of AG-grid grouping APIs, is that right? So maybe nothing we need to worry about, just checking if there's some tweak we would make to get it 100%

[haynesjm42]

Good catch, only an issue when using ag-grid grouping without full-row groups, but worthwhile to be correct

[amcclain]

If you haven't already, we should have a look over the calls to applyColumnState in AgGridModel also, to see if anything there needs to be (or could be) adjusted to account for changes to that API.