Bugfix: Keys not passing correctly due to config feature

[prkrtg]

I found a bug where requests were being dropped after I added the config feature.
This resolves it, both config based daemons or regular daemons are passing their keys correctly now

libby % python peers/peer_d.py -c peers/config.yml
[peer-D] routes: {'peer-B': 'tcp://127.0.0.1:5556'}
[peer-D] asking peer-B: perf.echo …
[peer-D] result: {'status': 'delivered', 'transid': '73f40c10f5c74217ab7ffd45db0e775b', 'resp': {'ok': True, 't0': 1763357105.4134872, 't1': 1763357105.415073}}
[PeerD] up: id=peer-D bind=tcp://*:5558
^C[PeerD] stopped
libby % python peers/peer_a.py                    
[PeerA] asking B: perf.echo …
[PeerA] result: {'status': 'delivered', 'transid': 'bd42e9b469c64ce0a2ff23f4bd541037', 'resp': {'ok': True, 't0': 1763357112.4434712, 't1': 1763357112.443878}}
[PeerA] published alerts.status
[PeerA] up: id=peer-A bind=tcp://*:5555
^C[PeerA] stopped