Update each Product Overview Page to include a cool Architecture diagram

[saralab]

Picture > 1000 words.

• Create a cool architecture diagram for each Product Overview page wherever applicable.
• For some cases ( like stack.js) In lieu of an Architecture diagram, a detailed "how does this fit in the Stacks' developer cycle as part of the Hiro Products" would be a great option.
• Also, think about using flow diagrams, conceptual diagrams to explain ideas and design
• A cool reference: https://github.com/ergomake/layerform

Before including these diagrams, we should address this related issue https://github.com/hirosystems/docs/issues/488

[ginny-d]

If I get the raw diagrams, I can rework them to standardize them

[ryanwaits]

related blocker: https://github.com/hirosystems/docs/issues/538