ci: Use ansible 2.19 for fedora 42 testing; support python 3.13

[richm]

NOTE: This also requires upgrading to tox-lsr 3.11.0

Ansible 2.19 will be released soon and has some changes which will
require fixes in system roles. This adds 2.19 to our testing matrix
on fedora 42 so that we can start addressing these issues.

python 3.13 is now being used on some platforms.

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Update CI workflows to test Ansible 2.19 on Fedora 42 and bump CI dependencies to support Python 3.13.

CI:

• Add Ansible 2.19 to the Fedora 42 testing matrix in integration and TFTP workflows
• Upgrade tox-lsr from 3.10.0 to 3.11.0 across all CI workflows to enable Python 3.13 compatibility

[sourcery-ai]

Reviewer's Guide

This PR updates the project’s CI workflows to test against Ansible 2.19 on Fedora 42 and upgrades tox-lsr to 3.11.0 across all GitHub Actions, ensuring compatibility with Python 3.13 platforms.

File-Level Changes

Change	Details	Files
Add Ansible 2.19 to Fedora 42 CI jobs	Bump env version for Fedora-42 in qemu-kvm-integration-tests.yml Update ansible_version for Fedora-42 in tft.yml	.github/workflows/qemu-kvm-integration-tests.yml .github/workflows/tft.yml
Upgrade tox-lsr dependency to 3.11.0 in workflows	Update pip install reference in qemu-kvm-integration-tests.yml Update pip install reference in ansible-lint.yml Update pip install reference in ansible-managed-var-comment.yml Update pip install reference in ansible-test.yml	.github/workflows/qemu-kvm-integration-tests.yml .github/workflows/ansible-lint.yml .github/workflows/ansible-managed-var-comment.yml .github/workflows/ansible-test.yml

---

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 @richm - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Review instructions: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

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