fix: clear stale message receiver cache for forwarded silo messages
Merged
RE
4mo ago+32+32+01234567890123456789-1-1-0123456789
Forwarded silo messages can arrive over a previous-hop connection. The receive path cached that connection as the message receiver, so responses could reuse a stale route and trigger wrong-target connection warnings.
This change only caches inbound silo connections when they match the sender, clears receiver caches before forwarding/rerouting, and reroutes stale cached connections through normal target placement.