[BFT Testing] ingress traffic - insecure/integration/*_test.go

[gomisha]

Context:

This issue captures the engineering efforts to fill-in the missing parts of enabling ingress traffic, as well as to develop an integration test involving all the components of the BFT testing framework such that:

The integration test is running on a mock engine A with a corruptible conduit and another honest engine B. Where both engines have their own separate networking layer (over stub network). An attack network is established and connects to the corrupted conduit factory that engine A resides on. Honest engine B is sending a message to corrupted engine A, i.e., an ingress message. The message should go through the attack network to a mock orchestrator that completely overrides its content with some fixture, and is routed back to engine A to be processed. The test is passed if engine A receives the corrupted message that the orchestrator composed on behalf of engine B.

Definition of Done:

• [x] All parts of corrupting ingress traffic are coming together.
• [x] Integration test is developed that captures the given scenario.