Bump Consul to version 1.22.7

What does this MR do?

Bump Consul to version 1.22.7

• Updates Consul to version 1.22.7.
• Keeps ConsulHelper::SUPPORTED_MINOR and the gitlab-ctl consul download default in sync with the packaged version.
• Records the module versions that 1.22.7 pulls in within the license decisions file: consul-awsauth, go-discover, golang-lru, memberlist, cap, go-secure-stdlib/awsutil/v2, and serf. license_finder does not recognise the HashiCorp MPL-2.0 license text on its own.

Risk: Consul 1.22.0 adds key name validation on the KV endpoint (DisableKVKeyValidation turns it off). Patroni stores plain path segments under service/<scope>/, so the validation does not affect it. The go 1.25.9 directive is satisfied by Go 1.26.4 in builder 5.66.0. The license decisions update follows the shape of the 1.21.4 bump; the build-package-on-all-os job will show whether any further module needs an entry.

Changelog: changed

Signed-off-by: Alec Xu axu@gitlab.com

Related issues

Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/10055

Backports

• 19-3-stable: !9732 (merged)
• 19-2-stable: !9733 (merged)
• 19-1-stable: !9734 (merged)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targets the appropriate branch.
• Component test plan copied into MR description. (No test plan file exists for Consul; the checks below cover the change.)
• Latest merged results pipeline is green.
• When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.
• Ensure the equivalent update for Cloud Native GitLab exists. (Not applicable: CNG does not ship Consul.)
• UBT version and corresponding checksum hash have been updated and referenced in the merge request if applicable. (Not applicable: Consul is built from source.)
  • UBT EE pipeline (Trigger:ee-package-ubt) is green

For GitLab team members

If you don't have permissions to trigger pipelines for this MR, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit. To debug QA failures, refer to Investigate QA failures.
• If config/software or config/patches directories are changed, build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline succeeded.
• If CI/CD configuration is changed, the branch is pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created or updated. (Not applicable: version pin only.)
• Tests added. (Not applicable: version pin only.)
• Integration tests added to GitLab QA. (Not applicable.)
• Equivalent MR/issue for the GitLab Chart opened. (Not applicable: the chart does not ship Consul.)
• Potential values for new configuration settings validated. (Not applicable: no new settings.)