Create/update architectural diagrams so we can develop a modernization approach

**Is your feature request related to a problem? Please describe the problem & source of request.**
We have some legacy systems/services that we need to modernize. We need to develop a modernization strategy and eventually an operational approach. To develop a strategy we need to:
1. understand the current and legacy architecture and how they interface and interact
2. understand the personas, and user journeys (at a high level) backed by analytics to prioritize experiences

**Describe the solution you'd like - Expected Behaviour**
To understand the legacy and current architecture we need up to date [C3 model](https://c4model.info/#what-is-the-c4-model) and/or architectural diagram(s) of our legacy systems so that:
1. we can begin to evaluate and prioritize modernization by service or component
2. we can begin using modern monitoring and scanning tools like [Tanzu](https://tanzu.vmware.com/developer/topics/modernizing-legacy-applications/), [Dynatrace](https://www.dynatrace.com/solutions/cloud-migration/), [RH Migration Toolkit](https://developers.redhat.com/products/mta/download), and other similar tools and services.
3. can be used when onboarding new people

**Describe alternatives you've considered**
Acceptable alternatives to C4 Model are Reflexion model (RM) : https://www.cs.ubc.ca/~murphy/jRMTool/doc/
Acceptable alternatives for monitoring and modernization tools will be evaluated based on architecture and priorities.

**Additional context & Screenshots**

Reach out to @faisal-hamood

No repository files or tests are named. Start by contacting @faisal-hamood and reviewing the attached diagrams, then inventory the legacy and current systems, their interfaces, and user journeys; done means an agreed C3 or Reflexion model is current enough to support modernization planning and onboarding.

Written by the indexing model from the issue text.