PipeWire: route portal responses per request


The screen capture helper subscribed to Request.Response with an empty
object path, i.e. to every request in the process, and dispatched
purely on its own m_operationState without checking which request a
response belonged to. This let concurrent QScreenCapture instances
observe each other's responses, and let a helper pick up responses to
requests an earlier, destroyed helper had abandoned, shifting its
state machine by one step.

The portal exports each Request under a path derived from our bus name
and a handle_token we choose, so subscribe to that specific path
before issuing the request, passing handle_token to CreateSession
(previously commented out). Stopping a capture now also drops the
subscription for any handshake still in flight. Tokens are allocated
fresh per request rather than cached and reused, using QUuid::Id128
since tokens become d-bus object path elements (only [A-Za-z0-9_]
allowed).

Pick-to: 6.12
Change-Id: I5a59497ae200cc95cd3bbf68f853e5622c86c375
Reviewed-by: Artem Dyomin <artem.dyomin@qt.io>
commitd2ae2aa07b40126158323de50da7060faa86e1db
parentd5316dee64c9ecf86808812ab0fad7da5c3f6f8b
authorTim Blechmann <tim.blechmann@qt.io>
committerTim Blechmann <tim.blechmann@qt.io>
commit timeWed, 2 Sep 2026 11:07:21 +0000