Add conditional python3-libdnf5 install for Fedora 41+ bootstrap

[PritamDutt]

Fedora 41+ systems use dnf5 as the default package manager, which requires python3-libdnf5 for Ansible compatibility.

This PR adds a conditional task to install python3-libdnf5 during bootstrap when:
ansible_distribution_major_version > 41

This ensures compatibility with newer Fedora releases while preserving behavior for older versions. The change is scoped, non-invasive, and aligns with the existing bootstrap logic in roles/bootstrap_os/tasks/fedora.yml.

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Ensures Ansible compatibility with Fedora 41+ systems by installing python3-libdnf5, which is required for interacting with the dnf5 package manager. Without this, bootstrap tasks may fail on newer Fedora hosts.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

• The task is added after the existing need_bootstrap check
• Scoped only to Fedora systems with major version > 41
• Uses raw module to match existing bootstrap style

Does this PR introduce a user-facing change?:

Fedora 41+ systems now install python3-libdnf5 during bootstrap to support dnf5-based package management. This ensures Ansible compatibility with newer Fedora releases.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: PritamDutt
Once this PR has been reviewed and has the lgtm label, please assign mzaian for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

• ✅login: PritamDutt / name: Pritam / (aea0557)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @PritamDutt!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @PritamDutt. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tico88612]

Could you consider integrating it (block / rescue) this way? You can cherry-pick my PR #12138 commit.

xref: #12138 (comment)

[yankay]

Thanks @PritamDutt
/lgtm
/ok-to-test