Candidate CandID Patch Fix

[lapadulamichael]

Brief summary of changes

This PR fixes candidate.CandID still being a signed int after running the upgrade patch. This was causing newly generated CandIDs to sometimes be out of range.

This is because the change to candidate.CandID's type being int(10) unsigned was done only in the schema and not included in the SQL/Archive/27.0/2025-02-05-Change-Candid-FK-To-ID.sql patch.

I added this to the archived patch and the release patch :

-- CandIDGenerator uses length of 10 unsigned int, this modifies table to avoid out of range generations
ALTER TABLE candidate MODIFY CandID INT(10) unsigned NOT NULL;