While the remote comms code that was recently merged (#578) contains some unit tests, the set of suite of tests could still majorly benefit from better coverage (particularly the things in the network.ts module). More significantly, though, we ought to have some form of end-to-end testing with respect to the remote comms functionality itself.

Note that existing end-to-end tests are end-to-end in the sense that the two ends are vats managed by a single kernel exchanging messages via a that kernel, whereas the remote comms features require two independent kernels communicating over the network via libp2p. Enabling such tests may entail a more substantial augmentation to our testing infrastructure.