better naming for nested and mapping in solvers

[mmckerns]

better naming for nested and mapping in solvers

edit solver interface to correspond to scipy conference paper

[mmckerns]

all solvers import through 'solvers', renamed BatchGrid? and Scattershot solvers; (see r465)

[mmckerns]

migrated StepMonitor? and EvaluationMonitor? to solver methods in r470

[mmckerns]

migrated constraints to solver method in r473

[mmckerns]

the remaining changes are in regard to "applying a Map" and "Nesting a solver"

solver = DifferentialEvolutionSolver(len(lb), 20) 
solver.SetRandomInitialPoints(lb, ub) 
solver.SetStrictRanges(lb, ub) 
solver.SetEvaluationMap(my_map) 
solver.Solve(my_model, COG) 

my_solver = PowellDirectionalSolver(len(lb)) 
my_solver.SetStrictRanges(lb, ub) 
my_solver.SetEvaluationLimits(50) 
solver = BuckshotSolver(len(lb), 20) 
solver.SetRandomInitialPoints(lb, ub) 
solver.SetGenerationMonitor(stepmon) 
solver.SetNestedSolver(my_solver) 
solver.SetSolverMap(my_map) 
solver.Solve(my_model, COG)

[mmckerns]

as of r680, nesting a solver works as above. So does applying a map -- however, the existing method names are not fully updated.

SetMapper should become "SetEvaluationMapper" or "SetGenerationMapper" or "SetSolverMapper" as appropriate.

[mmckerns]

going to split this into two... one for nested solvers (this one) and call it done...

and one for the potential renaming of mappers, in new ticket #219.