PipeWire: move event loop & context to QPipeWireInstance
We only want to use a unique event loop and a unique pw_context for both
screen capturing and audio IO, as having multiple is a bit of a waste of
resources.
They will have different core connections, though: audio IO connects to
the global instance, while screen capturing goes through the xdg dbus
portal.
As a drive-by, we unify the naming of the QPipeWireInstance instances
and ensure that `QSurfaceCaptureGrabber::updateError` is not called
under the pipewire event loop lock, as it may emit signals
Pick-to: 6.12
Change-Id: Iff11f0ad526cd634563d7bb38e157f1dac4703f7
Reviewed-by: Artem Dyomin <artem.dyomin@qt.io>