bootstrap: add explicit install of fuse-overlayfs

[brianmcarey]

What this PR does / why we need it:

fuse-overlayfs is no longer dragged in as a dependency in the latest bootstrap image. This causes the smaller jobs on the control-plane cluster to fail.

Installing fuse-overlayfs allows these jobs to pass successfully

$ podman run -ti quay.io/kubevirtci/bootstrap:v20240709-bdabeda rpm -qa | grep fuse
fuse3-libs-3.16.2-3.fc40.x86_64
fuse-libs-2.9.9-21.fc40.x86_64
fuse-common-3.16.2-3.fc40.x86_64
fuse3-3.16.2-3.fc40.x86_64
$ podman run -ti quay.io/kubevirtci/bootstrap:v20240607-febc467 rpm -qa | grep fuse
fuse3-libs-3.16.2-3.fc40.x86_64
fuse-libs-2.9.9-21.fc40.x86_64
fuse-common-3.16.2-3.fc40.x86_64
fuse3-3.16.2-3.fc40.x86_64
fuse-overlayfs-1.13-1.fc40.x86_64

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:

This should unblock the bump prow image PR - https://github.com/kubevirt/project-infra/pull/3491

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]

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-generate

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/cc @dhiller @xpivarc

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubevirt/project-infra/blob/main/OWNERS)~~ [dhiller] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment