centos9: Update provisioning container to Fedora 41

[brianmcarey]

What this PR does / why we need it:

Fedora 41 was released some time ago and Fedora 39 is getting close to EOL - upgrade the base provisioning container to Fedora 41.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/cc @dhiller

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from brianmcarey. For more information see the Kubernetes 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

[brianmcarey]

/test ?

[kubevirt-bot]

@brianmcarey: The following commands are available to trigger required jobs:

• /test check-gocli
• /test check-provision-alpine-with-test-tooling
• /test check-provision-centos-base
• /test check-provision-k8s-1.29
• /test check-provision-k8s-1.30
• /test check-provision-k8s-1.30-s390x
• /test check-provision-k8s-1.31
• /test check-provision-manager
• /test check-up-kind-ovn
• /test check-up-kind-sriov

The following commands are available to trigger optional jobs:

• /test check-up-kind-1.28
• /test check-up-kind-1.30-vgpu

Use /test all to run the following jobs that were automatically triggered:

• check-gocli
• check-provision-alpine-with-test-tooling
• check-provision-k8s-1.29
• check-provision-k8s-1.30
• check-provision-k8s-1.31
• check-provision-manager
• check-up-kind-1.30-vgpu
• check-up-kind-sriov

In response to this:

/test ?

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.

[brianmcarey]

/test check-provision-centos-base

[brianmcarey]

/test check-provision-centos-base

[brianmcarey]

/test check-provision-k8s-1.31-s390x