Implement Fee Schedule History (table, trigger, and backfill of 2025-01-03 snapshot)

[Jxio]

Introduce Fee Schedule History so that fee schedule changes are auditable:
add a history table and trigger to record changes going forward, and backfill the table with the 2025-01-03 snapshot produced in #32829.

Scope

• Database (migration)

• Create Fee Schedule History table (schema and columns as per design).

• Add trigger(s) on the relevant fee schedule table(s) to insert/update history rows on INSERT/UPDATE/DELETE.

• Backfill

• After the migration is deployed to the target environment, run a one-time load to insert the data from Ticket 32829 export into the history table, with effective/snapshot date 2025-01-03, as the first historical records.

[Jxio]

Columns
Data columns (mirror fee_schedules):
fee_schedule_id, filing_type_code, corp_type_code, fee_code, fee_start_date, fee_end_date, future_effective_fee_code, priority_fee_code, service_fee_code, variable, show_on_pricelist, gst_added.

change_on (required):
When this history row took effect. Populated in the trigger with CURRENT_TIMESTAMP (or equivalent) at the time of the change.

version (optional):
Version number per fee_schedule_id (e.g. 1, 2, 3…) for readability. Can be omitted if ordering by effective_at is enough.

changed_by (optional):
User or system that made the change. Can be set when changes go through the application (e.g. from session/context). Will often be NULL for direct DB changes.