chore: update python deps

[jdobes]

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

Refresh pinned Python dependencies across runtime and tooling requirement files to align with newer compatible versions.

Enhancements:

• Update core runtime dependencies (e.g. AWS SDK, gRPC, protobuf, Starlette, HTTP and TLS-related libraries) to newer compatible releases for improved stability and compatibility.
• Refresh supporting libraries and utilities (e.g. click, wrapt, yarl, kessel-sdk) to their latest compatible versions.
• Regenerate lock and requirements files to reflect updated dependency versions across build, dev, and extra environments.

[sourcery-ai]

Reviewer's Guide

This PR refreshes Python dependencies across the project (runtime, build, dev, and extras) by bumping pinned versions and updating their hashes to newer releases while keeping existing environment markers and overall dependency structure unchanged.

File-Level Changes

Change	Details	Files
Bump pinned versions for several core runtime libraries and regenerate hashes in requirements.txt to align with newer upstream releases.	Update aiohappyeyeballs, boto3, botocore, certifi, click, grpcio, idna, kessel-sdk, protobuf, python-multipart, s3transfer, starlette, wrapt, yarl, and zipp to newer patch/minor versions while preserving existing python_version and platform markers. Refresh all associated sha256 hashes for the updated packages to maintain pip hash-checking integrity. Keep the rest of the dependency list and constraints (including other packages and markers) unchanged to minimize behavioral differences.	requirements.txt conf/manager.env poetry.lock requirements-build.txt requirements-dev.txt requirements-extra.txt

---

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.

[github-actions]

SC Environment Impact Assessment

Overall Impact: ⚪ NONE

No SC Environment-specific impacts detected in this PR.

What was checked

This PR was automatically scanned for:

• Database migrations
• ClowdApp configuration changes
• Kessel integration changes
• AWS service integrations (S3, RDS, ElastiCache)
• Kafka topic changes
• Secrets management changes
• External dependencies

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

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.}

[jdobes]

/retest

[jdobes]

/retest