Added high-level architecture diagram

[esune]

Added a new "architecture" page with a diagram containing the overview of our services and how they connect to each other, to highlight inter-dependencies.

Notes:

• The OrgBook components were deliberately excluded from the diagram since the component is now in maintenance mode (no new issuers) and would have added significantly to the complexity of the picture. A separate diagram can be put together if needed for that piece.
• The diagram depicts the current showcase service, IF we shift to the showcase builder at some point it will need to be updated (I already have a draft saved that can be used).

[WadeBarnes]

Recommend adding connections between End User and BC Wallet, as well as End User and Showcase to depict the End User's direct interaction.

Might be worth calling out that the diagram does not include the following details (on prupose):

• Admin interaction with the various services - Traction, Endorser, etc.
• Interaction of the service with repositories - The services reading configuration from an external source such as the genesis file(s) for the CANdy networks, or (possibly eventually) the endorser's rule set.

[esune]

@WadeBarnes thank you for the suggestion, I added the end-user interactions to the diagram and a note below it regarding admin and external resources.

[loneil]

I don't know if the App Attestation controller is worth adding? It does interact between the BC Wallet and Traction.

[esune]

I don't know if the App Attestation controller is worth adding? It does interact between the BC Wallet and Traction.

Ohhh, good point! I completely forgot about it, let me see how I can add it to the diagram.

[esune]

@loneil added attestation controller and basic connectivity diagram (it's starting to be too many arrows now)