Create CAP History Tables

[franTarkenton]

Update the database to include CAP history table that can be used to track the changes to CAP events. Also create a cap area table that can be used to track changes between the relationship from caps to areas/basins for cap events.

Acceptance Criteria

• [x] tables defined in functioning alembic migration
• [x] migration completes locally
• [x] implemented in test instance

[franTarkenton]

CAP event status should only allow these values:

• create
• update
• cancel

Need to either create a domain or a lut to restrict this. Domain is easier as doesn't effect work already completed as much as implementing a lut would

[franTarkenton]

tests adjusted and passing when run locally with sqllite and postgres backends, however on postgres side they are persisting data in the database. This needs to get cleaned up

[franTarkenton]

see https://github.com/bcgov/nr-rfc-alertauthoring/pull/106