Remove temp index on vulnerability_occurrences

What does this MR do and why?

This MR removes a temporary index used to fix erroneously reused vulnerability identifiers.

This index was scheduled for removal on MR !126066 (merged)

migration up

main: == [advisory_lock_connection] object_id: 234780, pg_backend_pid: 85732
main: == 20230731210422 RemoveTempIndexVulnerabilityOccurrences: migrating ==========
main: -- transaction_open?()
main:    -> 0.0000s
main: -- view_exists?(:postgres_partitions)
main:    -> 0.0008s
main: -- indexes(:vulnerability_occurrences)
main:    -> 0.0166s
main: -- execute("SET statement_timeout TO 0")
main:    -> 0.0009s
main: -- remove_index(:vulnerability_occurrences, {:algorithm=>:concurrently, :name=>"tmp_idx_vulnerability_occurrences_on_id_where_report_type_7_99"})
main:    -> 0.0068s
main: -- execute("RESET statement_timeout")
main:    -> 0.0005s
main: == 20230731210422 RemoveTempIndexVulnerabilityOccurrences: migrated (0.0603s) =

Migration down

main: == [advisory_lock_connection] object_id: 224560, pg_backend_pid: 90832
main: == 20230731210422 RemoveTempIndexVulnerabilityOccurrences: reverting ==========
main: -- transaction_open?()
main:    -> 0.0000s
main: -- view_exists?(:postgres_partitions)
main:    -> 0.1072s
main: -- index_exists?(:vulnerability_occurrences, :id, {:where=>"report_type IN (7, 99)", :name=>"tmp_idx_vulnerability_occurrences_on_id_where_report_type_7_99", :algorithm=>:concurrently})
main:    -> 0.0046s
main: -- execute("SET statement_timeout TO 0")
main:    -> 0.0002s
main: -- add_index(:vulnerability_occurrences, :id, {:where=>"report_type IN (7, 99)", :name=>"tmp_idx_vulnerability_occurrences_on_id_where_report_type_7_99", :algorithm=>:concurrently})
main:    -> 0.0060s
main: -- execute("RESET statement_timeout")
main:    -> 0.0003s
main: == 20230731210422 RemoveTempIndexVulnerabilityOccurrences: reverted (0.1310s) =

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.