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

This commit updates a number of gems:

- gitlab-fog-azure-rm: This gem vendored a number of deprecated
Microsoft Azure client libraries and was the main blocker
to updating to Faraday 2.
(https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/merge_requests/48)

- graphlient: Full changelog:
  https://github.com/ashkan18/graphlient/blob/master/CHANGELOG.md

- Elasticsearch-related gems: These were pinned to 7.x presumably
since they still had Faraday 1 support, but we need to update to 8.x
for Faraday 2 support.

As mentoined in https://github.com/lostisland/faraday_middleware,
faraday_middleware is no longer needed supported for Faraday 2.
The JSON middleware is already bundled with Faraday 2.

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

Changelog: changed

As docs pages get moved around or deleted, docs links that we display in
the product might become outdated without us noticing.
This adds an ESLint rule that ensures `helpPagePath` always points to
files and anchors that still exist.
In future iterations, we should add a similar rule to check usages of
the `HelpPageLink` Vue component, and a Rubocop rule for the backend
`help_page_path` helper.

Report removed rules

Add e2e-test-pipeline-generate to validated jobs

Return the merged yaml if it is present

It does not belong in multiple database docs

Co-authored-by: Lin Jen-Shin <jen-shin@gitlab.com>

Improve output message and specs

More refactor

In case of an API error, merged YAML should be an empty Hash and not
empty Array. This API error can occur on forks because we cannot lint CI
config on forks.

Refactor with Job Struct

This is a major refactor commit

Finish refactor and unit tests

Suggest to use `feature_category: ...`.

Changelog: other

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

For Analytics Instrumentation review

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

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144174 we
introduced something we validates all newly added feature flag
definition files. But it's doing this by looking for all files in the
`config/feature_flags` directory. But since we introduced
https://docs.gitlab.com/ee/development/feature_flags/#optionally-add-a-patch-file-for-automated-removal-of-feature-flags
we allow people to optionally put a patch file for their feature flags.

Since the danger job is validating all newly added files this is
breaking any new MRs (e.g.
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149039 ) which are
adding patch files.

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

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

Add analytics instrumentation review for InternalEvents

Changelog: other
EE: true

We already check if the code includes `danger` but the suggestion
comment did not include it which can lead to confusion.

This should make the intention more clear and avoid messing up

Add some small edits to the source files, and regenerate the
main GraphQL reference file.

Skip warning if not running merged results pipeline

Catch JSON parser error

This reverts merge request !148160

We want to reduce the topmost 5% only.

Add a new test_level :tooling which contains:
- spec/dot_gitlab_ci
- spec/tooling

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

Before this commit this script was always silent.

- minor typo fix

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