Description of problem:
Update the libvirt pkgs in virt-launcher image to avoid the vm's logs spammed issue caused by libvirt

Version-Release number of selected component (if applicable):
cnv-4.12.3
virt-launcher-container-v4.12.3-9
libvirt-daemon-8.0.0-5.module+el8.6.0+14495+7194fa43.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Start a vm

2.Check the vm's log:
#oc rsh pods/virt-launcher-example-pnfsb tail -f /var/run/kubevirt-private/libvirt/qemu/log/default_example.log
2023-04-27 11:14:24.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:29.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:34.605+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:34.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:39.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:44.604+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:44.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:49.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:54.604+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:54.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:14:59.609+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:15:04.605+0000: Domain id=1 is tainted: custom-ga-command
2023-04-27 11:15:04.609+0000: Domain id=1 is tainted: custom-ga-command
...
3.

Actual results:
Spammed vm's log generated and it will cause no disk space issue.

Expected results:
No vm's spammed log generated.

Additional info:
This libvirt issue is fixed with libvirt-8.0.0-5.9.module+el8.6.0+18552+b96c5a91.Please see the link for details:
https://bugzilla.redhat.com/show_bug.cgi?id=2180032