Re: [meta-virtualization][wrynose][PATCH 1/2] libvirt: update to v12.2.0

Thanks for the wrynose backport.

This is a minor-release bump (12.1.0 -> 12.2.0), not a patch release —
the wrynose stable policy is 3rd-digit bugfix/security bumps only.
Same constraint I applied to the docker v29.4.3 patch a few weeks
back. The 12.2.0 NEWS specifically calls out new hyperv features,
IOMMUFD additions, and a new public API
(VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES) mixed in
with the security and bugfix work, which is what concerns me at the
stable bar.

Would you be willing to send a detailed breakdown of the v12.1.0 ->
v12.2.0 changes that addresses the new-feature side? Specifically,
for each new-feature item:

  - Is it gated behind an explicit build-time PACKAGECONFIG or
    runtime option?
  - Is it only active when external code calls a new API, or does
    it sit on a default code path?
  - Does it change any existing public API behavior?

If they're all opt-in or unreachable from a typical wrynose libvirt
configuration, I can take another look. Without that, I have to hold
this — and note that landing on master later wouldn't by itself change
the wrynose criteria; the new-features question still needs to be
answered for the stable branch specifically.

The paired meson ptest patch ([2/2]) waits with this one — same
response.

Tagging this and parking it pending the breakdown above.

Thanks.

Bruce