Remove fingerprint mechanism from ECA validation + endpoints
While initially, the fingerprint mechanism worked for what it was intended, it is causing issues with URLs shifting as PRs are updated which is not user-friendly. This feature was added to get around a bug with the persistence code we use that does not return the IDs of new records when generators are used. To properly resolve this issue, the issue with IDs will need to be solved first.
In place of the fingerprint, a new auto-incrementing id column will be used. This will identify a set of commits, and if passed, some basic validation will be done to ensure it is the same general request before updating. If either the group ID isn't passed or isn't valid, a new record will be generated to identify these requests. This will provide more stable URLs and easier lookups that don't make use of interpreted values that shift depending on content.