Insert 20181218192239 migration into `schema_migrations`
From https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24213#note_130387711, it appears this background migration isn't totally correct. While it probably won't cause any issues in production, it might be safer just to block this migration from running when RC4 gets fully deployed to avoid unnecessary errors and load on the database.