design easy-to-use interfaces

[gidden]

most of the grunt work of queries, etc., exist in the current code base, but, some of the capability can be collected in certain interface collections.

off the top of my head, I could imagine a metrics object that automates the process of producing certain growth and flow metrics. a prime example of object ease-of-use would be to create a CyclusSession object that simplifies the more descriptive method signatures that require a SQL session and simulation ID.