Make provenance in seasonal snapshots consistent with forecast and real-time

[aidan-short-gevernova]

• Updated seasonal snapshots schema to include a provenance array to match forecast and real-time. Each provenance item will contain a resource id and a proposals-considered array.
• Updated the max size of the proposals-considered array from 12 to 48 to support the possibility of 12 periods with 4 proposals each. This follows the assumption of 4 proposals per period made in forecast proposals considered.
• In addition to source and resource-id being required for each proposal-considered item, I also made period-start, period-end, cotinuous-operating-limit, and emergency-operating-limits required to match existing schemas.
• Updated the seasonal snapshot examples to match the new schema.
• Also adds custom seasonal snapshot header types rather than directly using common-header and base-header to match forecast and real time.

The spec looks like the following after the changes:

Closes #252

[getorymckeag]

Please also add a version number update on the spec to 1.1.1. I think we'll flag this as a bug fix, perhaps capture it with a few more bug fixes.

[getorymckeag]

Actually, never mind my prior comment about changing the spec. I propose we roll up a number of spec changes into an upcoming spec release.