fix(prometheus.receive_http): Bump prometheus patch for bugfix

[kgeckhart]

Brief description of Pull Request

Bump to prometheus patch release to pull in the fix for prometheus/prometheus#17659 which would impact prometheus.receive_http which uses the upstream remote.NewWriteHandler which was impacted by prometheus/client_golang#1927.

Issue(s) fixed by this Pull Request

Resolves: #5471

Notes to the Reviewer

I didn't add a test because it's a rather low level implementation details about returning response stats vs not returning response stats. I'm open to adding one though.

[github-actions]

🔍 Dependency Review

github.com/prometheus/client_golang/exp v0.0.0-20250914183048-a974e0d45e0a -> v0.0.0-20251212205219-7ba246a648ca — ⚠️ Needs Review

• Scope: This is the experimental module of Prometheus client_golang. It is explicitly not API-stable and uses pseudo-versions (commit SHAs). There are no tagged releases or formal changelogs for these ranges.
• Evidence:
  • Compare commits: prometheus/client_golang@a974e0d...7ba246a
  • The exp module typically evolves rapidly (new packages, symbol renames, API tweaks), and changes are not guaranteed to be backward-compatible.

What to check in your codebase

• Because this module is required directly in your root go.mod, it is very likely imported. Identify usages:

  grep -R --line-number --no-messages 'github.com/prometheus/client_golang/exp' .
  

• Common areas of usage in exp historically include experimental instrumentation (e.g., bridges, handlers, collectors). Verify constructors, option structs, and package paths for any changed/removed symbols.

Recommended process

1. Attempt a clean build and tests to surface compile errors:

   go clean -modcache
   go mod tidy
   go build ./...
   go test ./...
   

2. For any compile errors, open the diff above and the package docs at the new commit to map symbol/constructor/option changes.

Notes on code changes

• There is no published changelog for the exp module between these two SHAs. Without concrete changes referenced by the upstream repository, specific edits cannot be enumerated here.
• If compilation breaks due to renamed constructors or options, update call sites to the new names as indicated by the compiler errors and the upstream docs at the target commit.

If you need to defer risk

• Pin back to the previous commit until manual adaptation is complete:

  go get github.com/prometheus/client_golang/exp@a974e0d45e0a
  

github.com/prometheus/prometheus v0.308.0 -> v0.308.1 — ⚠️ Needs Review

• Scope: Patch bump within the same minor of Prometheus’ monorepo module. Typically includes bug fixes; API breakage is unlikely but Prometheus’ repo is large and not all internal packages are API-stable.
• Evidence:
  • Compare commits: prometheus/prometheus@v0.308.0...v0.308.1
  • No separate module changelogs are published for each internal package.

What to check in your codebase

• Identify which Prometheus packages you import (e.g., promql, tsdb, scrape, rules, discovery, model):

  grep -R --line-number --no-messages 'github.com/prometheus/prometheus' .
  

• Build and test to confirm no API shifts in the imported packages:

  go mod tidy
  go build ./...
  go test ./...
  

Expected code changes

• None identified from available public signals for this patch upgrade.
• If compiler errors arise, they will most likely be minor method or type adjustments in internal packages. Update call sites per the compiler guidance.

Notes

• No other dependency changes were detected in the provided go.mod diffs.
• For both upgrades, please rely on a full build/test cycle to surface any symbol or package-path changes, as there are no explicit upstream release notes covering these exact ranges.

[kalleep]

🚀