Persist checkpoints in evaluation history db

[JAORMX]

Summary

This starts adding ingest checkpoint data into the history log.

The main benefit here is that we'd have commit/branch information for git-related ingests.

artifacts require a little more work and will be handled in a separate PR.

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

coverage: 54.408% (+0.04%) from 54.365%
when pulling 2972c15 on checkpoint-history
into ba65aff on main.