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

When Sidekiq queues are added, or existing queues are changed, this can
have some impact on our infrastructure as we may have a change in
workload that leads to us needing to make an infrastructure change.

The Scalability team can help with this, so point to them as a first
step.

This is a preparatory step before we deprecate and move away from the
`backstage` label.

Next step will be removing references to `backstage`:
https://gitlab.com/gitlab-org/gitlab/-/issues/219751

See
https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/488#proposal


for the overall plan.

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

This removes the OOO/at capacity parts of the roulette logic since it's
now handled by the https://gitlab.com/gitlab-org/gitlab-roulette

 project
which updates and publishes roulette data every hour.

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>

With a recent update [0] to the bundle analysis we can provide the Job
ID of our current pipeline which will allow us to retrieve the correct
commits more reliably and link to the artifacts of the build job.

[0]: https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics/-/merge_requests/11

Adding a new danger job which analyses and compares the current MRs
bundle size to the bundle size of the commit on master it is trying to
merge into.

The tool itself is managed in:
https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics

**Why?**
- This might have been necessary when `gitlab-ui`
  was in its early stage. But now it's just confusing.
- Also, it's coupled with a `CSS Cleanup` label
  which isn't used consistently.
- Also, it has hard coded references to people
  regardless of availability.

This is to reduce duplication so that other Danger config can use this
helper method.

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

We don't want people to put the wrong labels just to disable the
"changelog needed" message from Danger.

- Labels should be set in accordance to the Throughput guidelines.
- Changelog should be added according to the "What warrants a
  changelog entry?" documentation.

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

Add option to send array to mr_has_label? and add tests
Refactor tests to use context

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

95c0aa51 introduced a new conditional on
changelog Dangerfile that is been triggered on security MRs. This commit
fixes that, as it's not a requirement to add a merge request ID on
changelogs for security merge requests.

The check to verify if the IID in changelog was set was
unintentionally removed in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27588.
This reverts that change.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/212323

Relates to https://gitlab.com/gitlab-org/gitlab/issues/29465

When an MR contains code changes in `ee/`, the `Changelog` probably
also needs to exists in `ee/`. So warn the author if that's not the
case. And the same for when the `Changelog` resides in `ee/` while
there are no other changes in `ee/`.

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

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

This now allows any file ending with `browser_spec.js`

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

Now that the single code base efforts are mainly over, we can remove the
special case hanfling from Danger bot