Make sure unsubscribe followed by subscribe returns new subscription


Since we could only have one subscription for each topic it was
not possible to return a new subscription when a subscription
request comes in on a topic that is scheduled for destruction.

We solve this by switching to a QMultiHash for the active
subscriptions, allowing more then one subscription for a
given topic. However, at most one of these subscriptions
are not present in the list of subscriptions scheduled to
be unsubscribed

This patch also changes multiple unsubscribes to the
same topic. Earlier all would return true, and
m_pendingUnsubscriptions would be updated for all
requests.
The new behavior is that only the first unsubscribe
is acted upon. Furthere requests will return false.

Fixes: QTBUG-135653
Pick-to: 6.8 6.9 6.10
Change-Id: I5a79efb68b3191e185325a89cc2042c773bb5c12
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@qt.io>
commitc383083270760d67c6fb415403518b941e1a28fe
parenta0a46333083e47837a11e248efae04d8e206059d
authorEven Oscar Andersen <even.oscar.andersen@qt.io>
committerEven Oscar Andersen <even.oscar.andersen@qt.io>
commit timeTue, 24 Jun 2025 13:14:36 +0200