chore: update technical architecture overview for pi14 (#323)

- Added Arch-Mojaloop-overview-PI14.svg:
  - Removed forensic logging sidecar (to make space)
  - Updated Settlement components to depict separate CGS & Rules functionality, and renamed components match new names
- Updates to Technical overview for PI14 main readme
- Added PI14 Technical overview page
- Updated summary to include PI14 Technical Overview page link

Co-authored-by: Sam <[email protected]>

SUMMARY.md

@@ -31,6 +31,7 @@
     * [Documentation Style Guide](contributors-guide/documentation/documentation-style-guide.md)
 * [Mojaloop Technical Overview](mojaloop-technical-overview/README.md)
   * [Mojaloop Hub](mojaloop-technical-overview/overview/README.md)
+    * [Current Architecture - PI14](mojaloop-technical-overview/overview/components-PI14.md)
     * [Current Architecture - PI12](mojaloop-technical-overview/overview/components-PI12.md)
     * [Legacy Architecture - PI11](mojaloop-technical-overview/overview/components-PI11.md)
     * [Legacy Architecture - PI8](mojaloop-technical-overview/overview/components-PI8.md)

mojaloop-technical-overview/overview/README.md

@@ -2,9 +2,9 @@
 
 There are several components that make up the Mojaloop ecosystem. The Mojaloop Hub is the primary container and reference we use to describe the core Mojaloop components.  
 
-The following component diagram shows the break-down of the Mojaloop services and its micro-service architecture: 
+The following component diagram shows the break-down of the Mojaloop services and its micro-service architecture:
 
-![Current Mojaloop Architecture Overview](./assets/diagrams/architecture/Arch-Mojaloop-overview-PI12.svg)
+![Current Mojaloop Architecture Overview](./assets/diagrams/architecture/Arch-Mojaloop-overview-PI14.svg)
 
 _Note: Colour-grading indicates the relationship between data-store, and message-streaming / adapter-interconnects. E.g. `Central-Services` utilise `MySQL` as a Data-store, and leverage on `Kafka` for Messaging_
 
@@ -15,10 +15,10 @@ These consist of:
 * The **Account Lookup Service** (**ALS**) provides a mechanism to resolve FSP routing information through the Participant API or orchestrate a Party request based on an internal Participant look-up. The internal Participant look-up is handled by a number of standard Oracle adapter or services. Example Oracle adapter/service would be to look-up Participant information from Pathfinder or a Merchant Registry. These Oracle adapters or services can easily be added depending on the schema requirements.
 * The **Quoting Service** (**QA**) provides Quoting is the process that determines any fees and any commission required to perform a financial transaction between two FSPs. It is always initiated by the Payer FSP to the Payee FSP, which means that the quote flows in the same way as a financial transaction.
 * The **Simulator** (**SIM**) mocks several DFSP functions as follows:
-    - Oracle end-points for Oracle Participant CRUD operations using in-memory cache;
-    - Participant end-points for Oracles with support for parameterized partyIdTypes;
-    - Parties end-points for Payer and Payee FSPs with associated callback responses;
-    - Transfer end-points for Payer and Payee FSPs with associated callback responses; and
-    - Query APIs to verify transactions (requests, responses, callbacks, etc) to support QA testing and verification.
+  * Oracle end-points for Oracle Participant CRUD operations using in-memory cache;
+  * Participant end-points for Oracles with support for parameterized partyIdTypes;
+  * Parties end-points for Payer and Payee FSPs with associated callback responses;
+  * Transfer end-points for Payer and Payee FSPs with associated callback responses; and
+  * Query APIs to verify transactions (requests, responses, callbacks, etc) to support QA testing and verification.
 
 On either side of the Mojaloop Hub there is sample open source code to show how a DFSP can send and receive payments and the client that an existing DFSP could host to connect to the network.

mojaloop-technical-overview/overview/components-PI14.md

@@ -0,0 +1,7 @@
+# Mojaloop Hub Current Components - PI14
+
+The following component diagram shows the break-down of the Mojaloop services and its micro-service architecture for pre PI14:
+
+![Mojaloop Architecture Overview PI14](./assets/diagrams/architecture/Arch-Mojaloop-overview-PI14.svg)
+
+_Note: Colour-grading indicates the relationship between data-store, and message-streaming / adapter-interconnects. E.g. `Central-Services` utilise `MySQL` as a Data-store, and leverage on `Kafka` for Messaging_