Improve the documentation to include architecture and organization information

[aschiefe]

It would be a huge help to those who are new to the project to have enhanced documentation so that a new person, such as myself, could read through the documentation and understand the project layout and the general components without the need to reverse engineer the project.

Specifically it would be nice to see the following in no particular order:

• Why things are organized in the way they are
• General architecture design
• General data flows, ie how data comes up from the k8 apis and into reportable data structures
• A more robust octant API documentation for both the exposed APIs and internal function calls

[wwitzel3]

Once #1079 is merged we will be migrating all documentation over to the storybook site, https://reference.octant.dev

[wwitzel3]

Feel free to ping me with questions about anything in here https://github.com/wwitzel3/octant-diagrams @davidmirror-ops