Co-authored-by: Peter Leitzen <pleitzen@gitlab.com>

This Dangerfile dates back to when we gradually adopted prettier. Now
our code base is fully prettier compliant and we have a separate
static-analysis job for prettier _and_ we run it part of lefthook. So
this Danger job just adds noise to the already long danger output and
potentially takes a long time.

Let's remove it, it outlived it's purpose.

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

Refactor with Job Struct

This is a major refactor commit

Finish refactor and unit tests

Suggest to use `feature_category: ...`.

To help make the migration process easier

This reverts merge request !154168

The current fallback note for an unfilled `feature_issue_url:` does not
provide enough context to make it obvious what it's referring to. This
MR adds the file path to direct the author of the MR in the right
direction.

Before:

```
- [ ] config/feature_flags/beta/flag_with_blank_feature_url.yml#L3: Consider filling `feature_issue_url:`
- [ ] Consider filling `feature_issue_url:`
```

After:

```
- [ ] config/feature_flags/beta/flag_with_blank_feature_url.yml#L3: Consider filling `feature_issue_url:`
- [ ] config/feature_flags/beta/flag_with_missing_feature_url.yml: Consider filling `feature_issue_url:`
```

To help make the migration process easier

Changelog: other
EE: true

Also add section about spacing and colors on official Tailwind docs
and update copy in danger rule

New method verifies all the necessary fields are set for removed metrics

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

Changelog: other
EE: true

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

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

Warn against using them prompt to instead use the Tailwind equivalent

When a file is just moved around it appears in the changed files list
but the diff is empty so we are skipping it.

This adds a new Dangerfile to do some Tailwind-related reporting.
Currently, we check whether the diff potentially contains interpolated
CSS utils. We might extend this rule to report additional info about CSS
utils usages.

We are using PNG instead of SVGs for compatibility with email
notifications.

Catch JSON parser error

This commit resolves the following warnings:
  gitlab/danger/saas_feature/Dangerfile:3:
    warning: already initialized constant Danger::Dangerfile::SEE_DOC
  gitlab/danger/feature_flag/Dangerfile:3:
    warning: previous definition of SEE_DOC was here

Ideally, the code should go into danger plugins to side-step any
namespace issues.

Add specs for ci template check tooling

Fix the formatting and file path with changes.category method

Add check! spec and fix a bug in existing code

Link to documentation page to provide in-depth information about
Reviewer Roulette.

- todo files should not be added to. They are meant for
  eventually resolving, not as a forever list of exceptions.

The checks here are superseded by the Pajamas Adoption Scanner,
implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/141368 and
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142704.

Part of https://gitlab.com/gitlab-org/gitlab/-/issues/367738.

- similar to update, destroy, etc, this method should require
  database review

Update the links in code and autogenerated docs

- from feedback

Also improve clarify messeage posted to run e2e test pipeline

- removed during initial deployment for backfilling, see
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133236#note_1600494778