[Backport staging-23.05] gst_all_1.*,python3Packages.gst-python: 1.22.4 -> 1.22.5

[github-actions]

Bot-based backport to staging-23.05, triggered by a label in #245736.

• Before merging, ensure that this backport complies with the Criteria for Backporting.
  • Even as a non-commiter, if you find that it does not comply, leave a comment.

[risicle]

Hold on, can we trim this down to just gst-plugins-ugly?

[lilyinstarlight]

Hold on, can we trim this down to just gst-plugins-ugly?

I think gstreamer does let you mix-and-match versions of the suite to some extent so it's possible that would technically work

But it should all be eligible for backport given it's a bug+security fix release and they release the entire suite at once (rather than individual components, other than gst-plugins-rs)

I suppose the alternative is doing one backport PR for gst-plugins-ugly (I forget the amount of rebuilds for the ugly plugin set alone, but it's possible that could go straight to release-23.05) and another for the rest of the suite

[lilyinstarlight]

@ofborg build gst_all_1.gst-devtools gst_all_1.gst-devtools.passthru.tests gst_all_1.gst-editing-services gst_all_1.gst-editing-services.passthru.tests gst_all_1.gst-libav gst_all_1.gst-libav.passthru.tests gst_all_1.gst-plugins-bad gst_all_1.gst-plugins-bad.passthru.tests gst_all_1.gst-plugins-base gst_all_1.gst-plugins-base.passthru.tests gst_all_1.gst-plugins-good gst_all_1.gst-plugins-good.passthru.tests gst_all_1.gst-plugins-ugly gst_all_1.gst-plugins-ugly.passthru.tests gst_all_1.gst-rtsp-server gst_all_1.gst-rtsp-server.passthru.tests gst_all_1.gst-vaapi gst_all_1.gst-vaapi.passthru.tests gst_all_1.gstreamer gst_all_1.gstreamer.passthru.tests

---

The ofborg aarch64-linux failure seems to be some transient test failure for pipewire. I couldn't get it to happen again on the community aarch64 builder, so I'm just requesting a new build from ofborg

[vcunat]

Sounds OK to take it all.