Store additional information in the Alembic version table

[C-Saunders]

I think it could be useful to have at least an updated_at (or similar) timestamp column on the Alembic version tracking table. For example, you might want to know exactly when your migration got run by your CI/CD system. Logs can potentially cover this in some cases, but I'd rather have it in the DB.

Alternatively, storing the history of migrations (hash + timestamp) could be useful. I've used other schema management libraries that took this latter approach and it came in handy once in a while to have this data.

[CaselIT]

Hi

this is mostly a duplicate of #1075 and #309.

Currently the maintainers don't have the time to implement it, but if it were contributed it would likely be accepted