Migration ID using local time

[jamillosantos]

Describe the bug

Migration source files are parsed have a date/time prefix, like 20200129225230_<migration name>. That date/time is known as migration ID.

The problem is that migration ID is being represented as local time. So when it gets persisted at the database it will be shifted.

To Reproduce

1. Create a source migration;
2. Runs it;
3. Go to the _migrations table at the database configured;
4. You should find the ID with a different date/time.

Expected behavior

The date/time should be parsed as UTC. So it should be absolute equal everywhere.