Fix dates of migrated log entries:

[rrennick]

Fixes #45

• Move the log migration to occur before the action record is deleted
• Add the source log entry datetime to the destination log entry
• Include the log entry date when getting an existing log entry
• Unhook the default action created log entry which uses the current time

@thenbrent , @JPry do you think I should look at a way to re-hook the action created hooks after the batch is done?

[rrennick]

@thenbrent Updated the PR per suggestions. Unit tests were also updated to use the new constructor. The one test failure was an instance of a timestamp being 1 second off.

[thenbrent]

@rrennick this is looking good. In answer to this:

do you think I should look at a way to re-hook the action created hooks after the batch is done?

Yes, definitely. The migration can be run by Action Scheduler, in which case, if we don't re-hook the logging, we won't get logs for both the remaining events, like completion, on the 'action_scheduler/custom_tables/migration_hook' action, as well as other actions run in the same queue.

It's probably a good idea to add new unhook()/hook() methods to handle this, similar to Migration_Scheduler::unhook()/Migration_Scheduler::hook().

[rrennick]

It's probably a good idea to add new unhook()/hook() methods to handle this

See https://github.com/Prospress/action-scheduler/issues/247

I added re-hooking for now since the comment store functions need to be done in AS. When I migrate it over I'll update this code to use the new functions.

[thenbrent]

LGTM. 👍