rm good_migrations

My opinion has changed over the years; I don't see value in maintaining
migrations when prod must be the single source of truth on the schema. Better
to pull the schema from prod than maintain a brittle set of scripts to
reproduce it.

Gemfile

@@ -51,7 +51,6 @@ gem 'rack-attack' # rate-limiting
 group :test, :development do
   gem 'capybara'
   gem 'database_cleaner'
-  gem 'good_migrations'
   gem "listen"
   gem "rspec-rails"
   gem "factory_bot_rails"

Gemfile.lock

@@ -111,9 +111,6 @@ GEM
     flamegraph (0.9.5)
     globalid (0.5.2)
       activesupport (>= 5.0)
-    good_migrations (0.1.0)
-      activerecord (>= 3.1)
-      railties (>= 3.1)
     hashdiff (1.0.1)
     hashery (2.1.2)
     htmlentities (4.3.4)
@@ -302,7 +299,6 @@ DEPENDENCIES
   factory_bot_rails
   faker
   flamegraph
-  good_migrations
   htmlentities
   jquery-rails (~> 4.3)
   json