Write energy and atomic data to file at every frame

[Jesse-V]

The ocore should write energy levels and atomic information to a file at every frame, possibly putting them all inside a folder so cleanup is easy. FAHClient provides an API call for gathering atomic information and the positions of all the atoms at each checkpoint which is then used by FAHViewer or by third-party visualizers. Your streaming core generates hundreds or thousands of frames on the local machine which can make protein animations much longer and more interesting, and since that data is local there's no need to send things over the network. Once the files are written to the disk, then it's relatively trivial for some middleware software to read the trajectory data and launch a visualization tool.

[proteneer]

We need to decide on this later, this probably won't be included in the MVP. I really dislike using raw files as an API. I'll leave this open for now.