Test multiple orderer groups by assigning different orderer groups to separate channels for both v2 and v3

e2e-network/docker/test-02-v2-raft-2orgs.sh

@@ -69,6 +69,8 @@ waitForContainer "orderer1.group1.orderer1.com" "Starting Raft node channel=my-c
 waitForContainer "orderer2.group1.orderer1.com" "Starting Raft node channel=my-channel1"
 waitForContainer "orderer2.group1.orderer1.com" "Starting Raft node channel=my-channel2"
 
+waitForContainer "orderer0.group1.orderer1.com" "Created and started new channel my-channel1"
+waitForContainer "orderer0.group1.orderer1.com" "Created and started new channel my-channel2"
 waitForContainer "orderer0.group2.orderer2.com" "Created and started new channel my-channel3"
 
 # check if org1 is ready
@@ -83,7 +85,7 @@ waitForContainer "peer1.org1.example.com" "Membership view has changed. peers we
 waitForContainer "db.explorer.example.com" "database system is ready to accept connections" "200"
 # // the next check is not working because explorer needs needs to be restarted first
 # // see the issue: https://github.com/hyperledger-labs/fablo/issues/604
-waitForContainer "explorer.example.com" "Successfully created channel event hub for \[my-channel1\]" "200"
+# waitForContainer "explorer.example.com" "Successfully created channel event hub for \[my-channel1\]" "200"
 
 # check if org2 is ready
 waitForContainer "ca.org2.example.com" "Listening on https://0.0.0.0:7054"
@@ -99,8 +101,8 @@ waitForContainer "peer1.org2.example.com" "Membership view has changed. peers we
 # check if chaincodes are instantiated on peers
 waitForChaincode "peer0.org1.example.com" "my-channel1" "chaincode1" "0.0.1"
 waitForChaincode "peer0.org2.example.com" "my-channel1" "chaincode1" "0.0.1"
-waitForChaincode "peer1.org1.example.com" "my-channel2" "chaincode2" "0.0.1"
-waitForChaincode "peer1.org2.example.com" "my-channel2" "chaincode2" "0.0.1"
+waitForChaincode "peer0.org1.example.com" "my-channel3" "chaincode2" "0.0.1"
+waitForChaincode "peer1.org2.example.com" "my-channel3" "chaincode2" "0.0.1"
 
 fablo_rest_org1="localhost:8802"
 
@@ -113,10 +115,10 @@ expectInvokeCli "peer0.org2.example.com" "my-channel1" "chaincode1" \
   '{\"success\":\"Jack Sparrow\"}'
 
 # invoke Java chaincode
-expectInvokeRest "$fablo_rest_org1" "my-channel2" "chaincode2" \
+expectInvokeRest "$fablo_rest_org1" "my-channel3" "chaincode2" \
   "PokeballContract:createPokeball" '["id1", "Pokeball 1"]' \
   '{"response":""}'
-expectInvokeCli "peer1.org2.example.com" "my-channel2" "chaincode2" \
+expectInvokeCli "peer1.org2.example.com" "my-channel3" "chaincode2" \
   '{"Args":["PokeballContract:readPokeball", "id1"]}' \
   '{\"value\":\"Pokeball 1\"}'