upgrade libvirt to "8th gen"

[prezha]

fixes: #9642

we've already upgraded from libvirt v3.9.0 to v7.4.0 (#13042)

recently, with v8, libvirt changed from github.com/libvirt/libvirt-go to libvirt.org/go/libvirt and this pr reflects that, which should, in turn, also ease future upgrades as well

my (light) local tests have shown no issues so far...

useful ref: libvirt API support matrix

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: prezha

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 [prezha]

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

[prezha]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 13440) |
+----------------+----------+---------------------+
| minikube start | 45.5s    | 43.8s               |
| enable ingress | 28.6s    | 28.7s               |
+----------------+----------+---------------------+

Times for minikube ingress: 29.1s 29.0s 30.0s 25.6s 29.6s
Times for minikube (PR 13440) ingress: 29.5s 29.6s 25.6s 29.1s 29.5s

Times for minikube start: 51.8s 43.8s 44.6s 43.8s 43.4s
Times for minikube (PR 13440) start: 45.1s 43.1s 43.2s 44.1s 43.6s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 13440) |
+----------------+----------+---------------------+
| minikube start | 29.1s    | 25.9s               |
| enable ingress | 22.9s    | 22.4s               |
+----------------+----------+---------------------+

Times for minikube start: 42.0s 25.5s 25.6s 25.9s 26.3s
Times for minikube (PR 13440) start: 25.5s 26.5s 26.4s 25.6s 25.5s

Times for minikube ingress: 22.9s 21.9s 23.4s 22.9s 23.4s
Times for minikube (PR 13440) ingress: 22.4s 21.9s 22.4s 22.4s 22.9s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 13440) |
+----------------+----------+---------------------+
| minikube start | 42.5s    | 44.4s               |
| enable ingress | 22.5s    | 20.1s               |
+----------------+----------+---------------------+

Times for minikube (PR 13440) start: 44.6s 46.0s 41.9s 44.7s 45.0s
Times for minikube start: 43.9s 41.3s 45.7s 41.0s 40.6s

Times for minikube ingress: 22.9s 23.4s 19.4s 23.4s 23.4s
Times for minikube (PR 13440) ingress: 19.9s 18.9s 23.4s 18.9s 19.4s

[medyagh]

I wonder if this test failure is related to this PR or not

for

https://storage.googleapis.com/minikube-builds/logs/13440/22345/KVM_Linux.html#fail_TestRunningBinaryUpgrade

	
	! 'kvm2' driver reported an issue: /usr/bin/virsh domcapabilities --virttype kvm failed:
	error: failed to get emulator capabilities
	error: invalid argument: KVM is not supported by '/usr/bin/qemu-system-x86_64' on this host
	* Suggestion: Follow your Linux distribution instructions for configuring KVM
	* Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/