'Full step' solution history calls should be handled in parent time solver class
'Full step' solution history calls should be handled in parent time solver class

Since the advance_timestep and adjoint_advance_timestep are called in user code, the
'full step' solution history calls should be made by the implementations of these functions
in the parent time solver class. These are now done by accessing the core time solver's
solution history object in the parent time solver functions.

dschwen/libmesh,libMesh/libmesh,jwpeterson/libmesh,BalticPinguin/libmesh,libMesh/libmesh,libMesh/libmesh,dschwen/libmesh,jwpeterson/libmesh,roystgnr/libmesh,dschwen/libmesh,jwpeterson/libmesh,roystgnr/libmesh,roystgnr/libmesh,dschwen/libmesh,roystgnr/libmesh,BalticPinguin/libmesh,jwpeterson/libmesh,jwpeterson/libmesh,dschwen/libmesh,libMesh/libmesh,dschwen/libmesh,dschwen/libmesh,libMesh/libmesh,jwpeterson/libmesh,dschwen/libmesh,roystgnr/libmesh,BalticPinguin/libmesh,roystgnr/libmesh,jwpeterson/libmesh,roystgnr/libmesh,jwpeterson/libmesh,libMesh/libmesh,libMesh/libmesh,BalticPinguin/libmesh,BalticPinguin/libmesh,libMesh/libmesh,roystgnr/libmesh,BalticPinguin/libmesh,BalticPinguin/libmesh,BalticPinguin/libmesh