Bump Prometheus to version 3.13.2 (19-3-stable)

What does this MR do and why?

Backports !9666 (merged) (Bump Prometheus to version 3.13.2) to 19-3-stable.

Prometheus 3.11.2 has reached EOL. 3.13 is an LTS release with support until July 2027, so this bump moves the stable branch back onto a supported version. It also resolves known vulnerabilities in dependencies of the currently bundled Prometheus 3.11.2 (see #10040, confidential).

Changes (cherry-picked from 40a0930e):

• config/software/prometheus.rb: bump Prometheus version from 3.11.2 to 3.13.2.
• support/dependency_decisions.yml: allowlist the MPL-2.0 licensed transitive Go dependencies pulled in by the new Prometheus version:
  • Relax the version pin on the existing github.com/hashicorp/go-version entry ([ v1.8.0 ] → []), since Prometheus 3.13.2 pulls in a newer version.
  • Add a github.com/hashicorp/nomad/api entry with no version pin, matching master.
• gitlab-ci-config/variables.yml: bump BUILDER_IMAGE_REVISION from 5.65.1 to 5.65.2. The 5.65.2 builder tag is cut from the 5-65-stable branch and includes only the Node.js 22.22.3 and pnpm changes backported in gitlab-omnibus-builder!505 (merged), which are required to build Prometheus 3.13.2. This keeps the stable branch on the 5.65.x builder line rather than jumping to 5.66.0.

Dependencies

• gitlab-omnibus-builder!505 (merged) (merged): backports the required Node.js 22.22.3 and pnpm changes to the 5-65-stable builder branch, released as builder tag 5.65.2.

Related issues

• Related #10031 (closed)
• Related #10040 (confidential)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes).
• This MR has a severity label assigned (if applicable).

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).