Add a additional ekms to the docker-compose

This MR extends the docker-compose by an additional KMS.

Description

The new setup created by running make compose-up looks then like this.

Which will be explained in more detail with the upcoming !34 (merged).

Motivation and Context

Two possible routes for key forwarding.

How Has This Been Tested?

Run config/configure-3ekms.sh

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

config/ekms/example01.yaml

@@ -6,10 +6,18 @@ AkmsURL: "http://172.100.20.22:4444/api/v1/keys/push_ksa_key"
 AkmsCkmsServerPort: "9696"
 Peers:
     # peer to ekms02
-    - PeerId: '968fd594-b0e7-41f0-ba4b-de259047a933'
+    - PeerId: '5e41c291-6121-4335-84f6-41e04b8bdaa2'
       PeerInterComAddr: 172.100.20.11:50910
       Sync: true
       # quantum module of type emulated at the given address
       QuantumModule:
           Type: emulated
           Address: 172.100.20.14
+    # peer to ekms03
+    - PeerId: 'f80db2c0-2480-46b9-b7d1-b63f954e8227'
+      PeerInterComAddr: 172.100.20.12:50910
+      Sync: false
+      # quantum module of type emulated at the given address
+      QuantumModule:
+          Type: emulated
+          Address: 172.100.20.18