Extend Cacti nodes and the consortium feature to support SATP

[RafaelAPB]

Understand and implement the easy formation of Cacti nodes for the purpose of operating a SATP network.

The process for consortium members to agree on privacy properties for view creation, processing, merging, and transfer is done in stage0. This issue creates a boilerplate for stage0 that populates bungee configurations for privacy in interoperability.

Requirements:

1. Add to SATP configuration privacy options (with respect to BUNGEE functionalities).
2. Expose those configurations in the form of Stage0 negotiation (issued against one or more SATP counterparty gateways that will be served by their own cactus node).
3. Allow Stage0 to happen at the consortium level (define spec to send a transaction to a Cactus node to perform stage 0 with a certain member of the consortium/all members)
4. The outcome of Stage 0 should be, among others, having SATP setting the configuration for BUNGEE.

Test case:
1 - Create a consortium of 2 Cacti nodes instantiated with SATP.

1. Perform a simple Stage 0 where both nodes agree to not to any processing to the views
   2 - Perform an end to end SATP transfer by calling one Cacti node belonging to one organization. That Cacti node should redirect the request to the other Cacti node, which then talks to the SATP plugin
   3 - Do the same for a consortium of 3 organizations running on different machines, over the network.
   4 - Understand latency tradeoff of the geographical diversity of the consortium.

The paper and packages/cactus-core-api/src/main/json/openapi.json and packages/cactus-core-api/src/main/typescript/generated/openapi/typescript-axios/api.ts might be useful.

[LordKubaya]

hi

[eduv09]

@RafaelAPB I'll try to tackle this one

[RafaelAPB]

Include injecting policy no SATP