RHINENG-26324: go packages security update

[MichaelMraka]

Secure Coding Practices Checklist GitHub Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

Summary by Sourcery

Update Go module dependencies to newer versions for security and maintenance.

Enhancements:

• Bump github.com/jackc/pgx/v5 to v5.9.2.
• Upgrade golang.org/x/crypto, golang.org/x/net, and golang.org/x/sys to their latest minor versions.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates several indirect Go module dependencies (pgx and multiple golang.org/x libraries) to newer patch/minor versions to pick up security and bug fixes, without any accompanying code changes.

File-Level Changes

Change	Details	Files
Update PostgreSQL driver dependency to latest v5 patch for security/bug fixes.	Bump github.com/jackc/pgx/v5 from v5.8.0 to v5.9.2 in go.mod Ensure go.sum is updated accordingly for the new pgx version	go.mod go.sum
Update core golang.org/x libraries to newer versions to address security advisories and benefit from upstream fixes.	Bump golang.org/x/crypto from v0.51.0 to v0.52.0 in go.mod Bump golang.org/x/net from v0.54.0 to v0.55.0 in go.mod Bump golang.org/x/sys from v0.44.0 to v0.45.0 in go.mod Ensure go.sum is updated accordingly for the new golang.org/x versions	go.mod go.sum

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The dependency bumps in go.mod don’t appear to be accompanied by the corresponding go.sum updates; please run go mod tidy (or equivalent) and commit the resulting go.sum changes so the module graph is consistent.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The dependency bumps in go.mod don’t appear to be accompanied by the corresponding go.sum updates; please run `go mod tidy` (or equivalent) and commit the resulting go.sum changes so the module graph is consistent.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.20%. Comparing base (e91c723) to head (8178f44).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2212      +/-   ##
==========================================
- Coverage   59.23%   59.20%   -0.04%     
==========================================
  Files         137      137              
  Lines        8795     8795              
==========================================
- Hits         5210     5207       -3     
- Misses       3037     3040       +3     
  Partials      548      548              

Flag	Coverage Δ
unittests	59.20% <ø> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.