Condense headers tables

[KaylaCrush]

right now, when we save, if there is already a header with the same characteristics AND same date range it will stop the whole thing. But hey the thing is, a lot of the info in the headers table is just repeated over and over again, because the same orgs are there year after year. I could just collapse that all into one tab.e!

Upsides: Way fewer header tables seems good

Downsides: what if info about a place changes year after year? That should be reflected in the data I GUESS? Or.... maybe I only need the latest values? Just update the old stuff.

[KaylaCrush]

Other duplication: In the modern lobbying activity tables, lots of rows will have the same client/lobbyist combo, being from the same table. I could move that to another join table, like I did with headers??

[KaylaCrush]

ultimately an idealized form of this would go

table for each lobbyist/entity with latest header info and a unique header id

table for each disclosure page that would store url, date range, header id, and a unique generated disclosure id

then, rather than referring to the headers, each row from a table would reference the disclosure id it was pulled from