Remove stale docs

[johnthagen]

• Remove stale docs that have not been updated for 1.5 years. These docs will likely continue to rot and likely the best place to get definitely information about the structure of the project and API is in the respective backend and frontend source projects where things will be current.

Question: Should we also migrate docs/meeting_notes and docs/Requirements for RWC Appliance.pdf to somewhere else such as Google Drive?

---

This change is 

[jasonleenaylor]

Reviewed 2 of 59 files at r1.
Reviewable status: 2 of 59 files reviewed, all discussions resolved (waiting on @johnthagen)

[jasonleenaylor]

I think keeping the historic docs in the repo is better then losing them somewhere else. We are capturing things from user interaction in github issues now so we won't be adding to that. If we decide they are completely useless to us we can remove them.

[jasonleenaylor]

I do want to look over those docs again to make sure we have everything important captured in issues.

[johnthagen]

Reviewed 59 of 59 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved