Keep migrations consistent after Rails upgrades

[thoughtbot-summer]

We recently upgraded a project from Rails v6.1 to v7.0, which changed the default precision for datetime columns from nil to 6. PgParty currently calls ActiveRecord::ConnectionAdapters::SchemaStatements#create_table (and #change_column_null) directly, which doesn't include the backwards compatibility provided by ActiveRecord::Migration::Compatibility. Thus, re-running our existing migrations generated those datetime columns with precision: 6 instead of precision: nil.

This change uses Proc#binding/Binding#receiver to call those methods on the ActiveRecord::Migration instance instead, which includes that backwards compatibility.

Thank you!

[rkrage]

Thanks for the PR and all the context!

It seems like this should work but it feels a little strange. I'm going to dig into this a bit to see if maybe there's an alternative approach. I should probably write some migration compatibility tests too. Seems like a pretty big miss on my end...

[rkrage]

Sorry, haven't really had time to look into this. Gonna go ahead and merge