Add persistence to commit validation results
There should be the persistence of the results for the Git ECA validation checks. This will allow for lookups of already validated commits, bypass the mechanism through direct data manipulation, and enable future functionality in viewing results after checks through a unique key.
Information that should be stored includes the following:
- Usernames/email of user authoring commits
- This will include the future option of provider username which will be used in future versions
- The validation errors for the commits
- These errors should match up to the errors used in Drupal where possible for easier migration
- When the commit was last and first validated
- Storage of a unique key to link a set of commits together for later lookup
- This key should be generated through a combination of the composite key parts of the initial lookup. Those composite parts should include the project, SHA, and repo that this commit is linked to.
- We will need to ensure that this mechanism is somewhat robust and won't be broken by repository migrations, or at least can have actionable migration activities.