Consider devops usecases; refactor GO API documentation

[kltm]

A follow-on from #70 .

After running through the documentation, we're thinking that it might be good to refactor the doc into three parts:

1. devops environment setup; may be generally useful for other projects as well
2. general utility and terraform use; may be useful for other projects as well
3. GO API-specific test and deployment workflow, including names, how to get a fix out, etc.; includes how we want to run devops, names to use, etc.

Currently slated for next general software meeting.