Recreate index for security builds to include fuzzing jobs

What does this MR do and why?

We have to recreate index for ci_builds to include apifuzzer_fuzz and apifuzzer_fuzz_dnd security jobs.

This is a first MR for this process according to https://docs.gitlab.com/ee/development/adding_database_indexes.html#create-indexes-asynchronously

Migrations

⋊> env VERBOSE=true bundle exec rake db:migrate:down VERSION=20220224204415
== 20220224204415 RecreateIndexSecurityCiBuildsOnNameAndIdParserWithNewFeatures: reverting 
-- rename_index("ci_builds", "index_security_ci_builds_on_name_and_id_parser_features_old", "index_security_ci_builds_on_name_and_id_parser_features")
   -> 0.0012s
== 20220224204415 RecreateIndexSecurityCiBuildsOnNameAndIdParserWithNewFeatures: reverted (0.0025s) 

⋊> env VERBOSE=true bundle exec rake db:migrate:up VERSION=20220224204415
== 20220224204415 RecreateIndexSecurityCiBuildsOnNameAndIdParserWithNewFeatures: migrating 
-- rename_index("ci_builds", "index_security_ci_builds_on_name_and_id_parser_features", "index_security_ci_builds_on_name_and_id_parser_features_old")
   -> 0.0016s
== 20220224204415 RecreateIndexSecurityCiBuildsOnNameAndIdParserWithNewFeatures: migrated (0.0036s) 

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.

Related to #344264 (closed)