ELECTORAL REGISTRATION INTEGRATION — BACKEND FOUNDATION

This update adds:
- SQL mapping table ec_registration_forms to associate one Electoral Data Collections form with an election and map student number, full name and optional email question IDs.
- On submission of a linked Electoral-scope collection, the response handler checks the student number against an active students record and active student user account.
- Submitted full name must match the official student account name. If an email question is mapped and populated, it must match the official email.
- Matching students are automatically inserted/updated as approved in that election's ec_voters register.
- Invalid/nonmatching submissions remain recorded as collection responses but are not added to the voter register.
- Existing staff candidate photograph upload endpoint remains available; candidate photos are managed by staff.

NOT A COMPLETE DEPLOYABLE FEATURE YET
The administrative UI for selecting a published Electoral Data Collection, mapping its question IDs, and viewing link status has not yet been added. Do not deploy this as a completed end-to-end workflow until that UI is implemented and tested.
The supervised ballot screen that displays approved candidate photos/profiles also remains a later implementation task. The legacy public election endpoint remains disabled; do not enable public voting.
Apply the included migration only once after the previous Electoral Commission and Phase 2 migrations.
