First step towards having a DB save and restore function available in the framework.  Note that most of the code change is working around a limitation in PP regarding imports.  Not functionally complete yet
Steps toward sqlite cache and restore - doesn't work due to concurrent updates to the DB?  Bad design in general since update happens on server side.  Will reuse code, but rearchitected slightly.
Refactoring result handling out of the job manager
A working version that records all the param/result pairs in a sqlite3 database.
Add auto-recovery using previously run sample points.  Note that this code is not mature - there's all kinds of caching staleness hear which could result in incorrect results.  You are expected to know what you're doing