Renumber migrations to use null-safe type trigger

After switching to `type_new` we need the new version of this trigger
from !80537,
otherwise we can't set `type_new` in the specs.

db/schema_migrations/20220209121410

-d769aa29da02448f83f87bc67adc83793bb59ff74b9452f16be6d5d20e6b5f98
\ No newline at end of file

db/schema_migrations/20220209121435

-6f18a3235313ff0cb3f0e63683351385e76cd404b5a765c8e9f841dc91e02cae
\ No newline at end of file

db/schema_migrations/20220425121410

+73ab85c5ef724f6aba4a964f42e586db0a198affd134ba598189629fb95989a4
\ No newline at end of file

db/schema_migrations/20220425121435

+fd00d3d8104cba09134853976cf4f1dea7abb5e1dd2c4ea8b46adc4742c71030
\ No newline at end of file

spec/lib/gitlab/background_migration/backfill_integrations_enable_ssl_verification_spec.rb

@@ -2,7 +2,7 @@
 
 require 'spec_helper'
 
-RSpec.describe Gitlab::BackgroundMigration::BackfillIntegrationsEnableSslVerification, schema: 20220209121435 do
+RSpec.describe Gitlab::BackgroundMigration::BackfillIntegrationsEnableSslVerification, schema: 20220425121410 do
   let(:migration) { described_class.new }
   let(:integrations) { described_class::Integration }