Reset column configuration when database changes.  

This is necessary because the header_state blobs break between versions.

Also set up some much nicer column width defaults so it's not such a shock when a users' settings are blown away
Hm, though schema upgrades are not the only way this bug occurs -- for example we could add another fake column like "preview" and it would happen.