We're using the housekeeper gem here to generate the `.rubocop_todo`
files and create an MR.

Run `bundle exec gitlab-housekeeper -d -k Keeps::GenerateRubocopTodos`
to test out the changes locally.

Reduce branch name length
Refactor description and link
Divy MRs evenly to team members

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Add gdk start db to dry run instruction

Update MR description

It generates migration to remove indexes as post migrations. It
also remove the duplicated index from duplicate indexes list

Changelog: changed

Signed-off-by: Rémy Coutable <remy@rymai.me>

Co-authored-by: Madelein van Niekerk <mvanniekerk@gitlab.com>

The OverdueFinalizeBackgroundMigration  keep is a script that is run in
CI for generating merge requests to
[finalize batched background migrations](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#finalize-a-batched-background-migration).

Per our documentation we can only finalize a batched background
migration added before the last "required stop" which is the minimum
versin someone must upgrade to before they can upgrade to this version
of the code.

We were hardcoding that version in the keep before but now we have
MIN_SCHEMA_GITLAB_VERSION which is exactly for this purpose we don't
need to hardcode it anymore. We also changed from `<` to `<=` now that
this version refers to the version of the last required stop rather than
the first version after it.

Also extract some shared logic to Groups helper

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

This keep uses test database to look for duplicated
indexes and it creates each respective MR to drop
each index.

Changelog: added

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Move RuboCop autocorrect call into a helper method so it's easier to
reuse.

Pass existing logger instance to allow keeps to log.

Signed-off-by: Rémy Coutable <remy@rymai.me>

This change will allow the `RelatedIssueFinder` class to detect the
issue for the `AddQuarantineLabelsToRelatedIssue` processor in
`triage-ops`.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

This `force: true` option seems to generate the migration even if there
is an existing migration with the exact same name. Additionally it
deletes the existing migration with the same name. This is probably not
something we ever intended to do so I'm removing it.

At some point we may want to update this to skip finalizing a BBM if a
migration with a matching name exists (or generate a guaranteed unique
name) but it's not clear to me if we actually have a use case for this
now. Also there are plans to be more strict about not re-using batched
background migrations so possibly the matching name won't be very common
in future.

The `gitlab-housekeeper` currently has a very simple implementation of
automatically removing feature flags that are past their expected usage
date.

This MR introduces new functionality to `Keeps::DeleteOldFeatureFlags`
where it looks for a `.patch` file matching the same name as the `.yml`
file for the feature flag. If it exists it will apply the patch.

The tool will be used to fully automate the developer workflow for
removing feature flags. Instead of developers needing to remember to
remove their feature flag later they can just add a `.patch` file when
they first create the feature flag. Later on the `gitlab-housekeeper`
will come along and clean it up for them.

This was not working for 2 reasons:

1. The YML file URL was pointing to the HTML version and was not
   returning valid YML. It's been updated to the raw path now.
2. The YML from this URL contains more keys than just `version` and
   `date` so we needed to ignore those other keys when constructing our
   `Struct`

Otherwise, we are seeing the following exception on Ruby 3.0:

    Failure/Error: actual_changes = keep.each_change(&:itself)
     ArgumentError:
       unknown keyword: :permitted_classes

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>