muster release v5.34.4

muster test names who holds a Valkey stand-in’s port. A scenario on Valkey storage failed now and then in CI with failed to start valkey on 127.0.0.1:<port>: bind: address already in use, and nothing said which socket held the port. The allocator had handed it out from outside the ephemeral range, behind a guard. The failure now carries the socket table for that port (local and remote address, state, owning pid and command line where visible), as instance startup failures already do. (#1356)