danger: Use changelog rule from gitlab-dangerfiles

What does this MR do and why?

This updates gitlab-dangerfiles to 2.9.2 which includes the following main changes:

• Introduce a new type_label rule (merge request)
• Introduce a new Helper#has_scoped_label_with_scope? method (merge request)
• Add a new z_add_labels rule to add labels (merge request)
• Introduce Helper#mr_source_project_id and Helper#mr_target_project_id (merge request)
• Add #labels_to_add to Helper (merge request)
• Import the changelog rule (merge request)

Screenshots or screen recordings

Below are examples to show that the behavior is the same regarding the changelog Danger rule, which is now part of gitlab-dangerfiles.

When changelog is missing:

When the EE: true is set but no ee/ changes are present:

How to set up and validate locally

I needed to add CI_PROJECT_DIR=. to the Danger command in lefthook.yml since it's required to load the .gitlab/ci/changelog_config.yml file.

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.