The clients now block until the channel is in the READY state. This
fixes some test flakiness issues we have had.

Add response parameters to custom_metadata streaming request for Node and PHP
clients.

The Java server does not respond with separate initial and trailing
metadata when there is no response data - it is only emiting the
requested trailing metadata. Adding the response parameters to the test
(in accordance with the specification) avoids this, but I will open a
separate issue to investigate the Java behavior.