option to enable logging of data to a file or a socket (e.g. --data_log_location log.csv/.sqlite)

[wis]

Checklist

• I've looked through the documentation and existing open issues for similar feature requests.

Describe the feature request

It would be nice to have a feature where the updates to the table are logged to disk, I would like to analyze the data to draw conclusions from the data over a longer time frame, like how does e.g. Chromium's memory usage balloon up with time as I use it, or which long running process used the most CPU resources today?

Instead of writing to a file, It would also be useful if bottom outputs the data to a socket, and not necessarily in CSV format, over a socket updates in e.g. JSON would work too.

On my system, bottom running in the background all the time takes between 0.1% to 0.4% of the CPU resources, it would be nice if you could pay this cost once, for one instance of bottom, and not need to have a second program also running and constantly querying the running processes just for logging.