Double check migrations

[edgrosvenor]

The goal is to be able to use what we know about each column from the Doctrine type as well as (at least in the case of enum columns) the actual data from the column to create a migration that will perfectly create the column. There's not exactly a 1:1 relationship between what Doctrine can learn about a column and what Laravel uses to create its migrations. So there is likely room for improvement here.