Visible columns not saved

[krisavi]

Describe the bug
When changing visible columns there is no way to save the view. Any update will reset to default set of columns that doesn't even have host config action visible.

To Reproduce
Steps to reproduce the behavior:

1. Go to web interface
2. Change visible columns
3. Refresh
4. Columns are being reset

Expected behavior
When changing visible columns save the set into browser session at least.

Desktop (please complete the following information):

• MacOS 15.1
• FireFox 131.0.3 (aarch64) / Google Chrome 130.0.6723.70 (Official Build) (arm64)
• pgwatch built on aarch64 MacOS for amd64 linux with Remove hardcoded pgwatch user in config schema creation #580 change.

[krisavi]

It is big enough annoyance that I would classify it more like bug than feature request. Generally normal expectations is that there is some kind of saving of settings. If it wasn't the normal expectation, then I would have classified it as feature request.

[pashagolub]

@tvecerakb taking into account the perfect job done in #618, are there any chances you can help us with this one? :)

[ay-bh]

@pashagolub I have solved this and will create a PR in a couple of hours.

My solution is to create a useGridColumnVisibility hook that manages the column visibility state for MUI DataGrids with persistent storage. It takes a storage key parameter, initializes the visibility state from localStorage (or an empty object if no saved state exists), provides a callback to handle visibility changes that updates both the state and localStorage, and returns the current visibility model along with the change handler. This approach allows all the grids in the application (Presets, Sources, Metrics) to maintain their own persistent column visibility preferences across sessions.

[ay-bh]

@pashagolub I’ve raised a PR. Could you take a look when you have a moment? Let me know if any changes are needed. Thanks.