Sub collective RPC uses wrong subjects but ping works #2167
Description
>>> [8] Message received 2024-04-22T19:21:22+02:00 on subject iot.node.x
╓─ Transport ─────────────────────────────────────────
║
║ io.choria.protocol.v2.transport message with 2.3 KiB payload from example.net
║
║ Payload Protocol: io.choria.protocol.v2.secure_request
║ Reply-To: choria.reply.7419405695a186147a0de38f7e31a509.2fStoRv4HVstNxy1hHonvl14VCE
║ Federated: false
║
║ ╓─ Secure Request ─────────────────────────────────────
║ ║
║ ║ io.choria.protocol.v2.secure_request message with 352 B payload
║ ║
║ ║ Payload Protocol: io.choria.protocol.v2.request
║ ║ Signature: acd496e6b8aac1036194e8dc085812...ad8b3354a27a594c040b02c8a4c10d
║ ║ Caller: up=rip
║ ║ Signer: aaa_request_signer
║ ║
║ ║ ╓─ Request ────────────────────────────────────────────
║ ║ ║
║ ║ ║ io.choria.protocol.v2.request message with 45 B payload
║ ║ ║
║ ║ ║ Request: 2fStoRv4HVstNxy1hHonvl14VCE
║ ║ ║ Sender: example.net
║ ║ ║ Agent: rpcutil
║ ║ ║ Caller: up=rip
║ ║ ║ Collective: iot
║ ║ ║ Time: 2024-04-22T17:21:21.768043441Z (0.29s ago)
║ ║ ║ TTL: 60
║ ║ ║ Agent Filter: rpcutil
║ ║ ║ Payload: {"agent":"rpcutil","action":"ping","data":{}}
║ ║ ║
Here we can see a message sent to iot.node.x has reply-to choria.reply.7419405695a186147a0de38f7e31a509.2fStoRv4HVstNxy1hHonvl14VCE in the wrong subcollective.
This worked, despite the bug, in protocol1 but in 2 where things are locked down this fails as the iot nodes cant reply to choria sub collective