RAFT test with large number of channels

Attachment observations.txt describes many confusing logs and potential issues; we will open bugs to track each unique one to capture investigation explanations (and fixes where needed). Marked as Executing because we are rerunning variations of this testcase with different numbers of channels and traffic volume in an effort to identify what we can support in our test environment without those problems: 0: change logspec to WARNING in orderers 1. Create 500 channels, and run traffic on 50. 2. If that looks ok, then (still with 500 channels) run traffic on 100. 3. If that looks ok, then increase by 50. Repeat until problems resurface, and then investigate. 4. Repeat where we left off, but this time change the port used for step messages so that it is different than the one used for invokes. Maybe that will help. Refer to: Orderer_General_Cluster_ListenPort Orderer_General_Cluster_ListenAddress Orderer_General_Cluster_ServerCertificate Orderer_General_Cluster_ServerPrivateKey