Noop migrations containing faulty SQL regex
What does this MR do?
We had a mistake in our SQL regex, spotted by @a_akgun (!67687 (comment 649843625)) This MR noop
s the already merged migrations that relied on that regex, and removes the temporary index (if existing) generated by them.
Related to #330276 (closed)
Database
== 20210816161107 RemoveIndexContainingFaultyRegex: migrating =================
-- transaction_open?()
-> 0.0000s
-- indexes(:merge_requests)
-> 0.0246s
-- current_schema()
-> 0.0002s
== 20210816161107 RemoveIndexContainingFaultyRegex: migrated (0.0295s) ========