Always compute single point map when computing Jacobian
Always compute single point map when computing Jacobian

As shown in libmesh/libmesh#2997, when the threshold for
determining non-affine is very low, e.g. if we make our affine
determination to a much tighter tolerance, then it's possible
to see discontinuities in a contrived test like the one changed here.
As described in the referenced libmesh pull request, if elements
are affine, then the user Jacobian evaluation routine will treat them
as such, but a slight perturbation to the displacement field, as is done
in finite difference testing of the Jacobian, will make the element
non-affine and consequently proceed down a different code path in
function evaluation. The solution is to make sure that when performing
Jacobian evaluations and our affine map determination is a function of
nonlinear degrees of freedom (e.g. the displacement variables) that we
always compute the single point map

sapitts/moose,milljm/moose,sapitts/moose,sapitts/moose,lindsayad/moose,SudiptaBiswas/moose,milljm/moose,dschwen/moose,idaholab/moose,laagesen/moose,idaholab/moose,harterj/moose,bwspenc/moose,andrsd/moose,lindsayad/moose,jessecarterMOOSE/moose,dschwen/moose,andrsd/moose,harterj/moose,idaholab/moose,milljm/moose,SudiptaBiswas/moose,dschwen/moose,sapitts/moose,lindsayad/moose,bwspenc/moose,harterj/moose,SudiptaBiswas/moose,laagesen/moose,jessecarterMOOSE/moose,SudiptaBiswas/moose,dschwen/moose,bwspenc/moose,nuclear-wizard/moose,laagesen/moose,jessecarterMOOSE/moose,harterj/moose,andrsd/moose,bwspenc/moose,nuclear-wizard/moose,milljm/moose,nuclear-wizard/moose,andrsd/moose,laagesen/moose,milljm/moose,laagesen/moose,lindsayad/moose,SudiptaBiswas/moose,lindsayad/moose,jessecarterMOOSE/moose,dschwen/moose,idaholab/moose,nuclear-wizard/moose,idaholab/moose,jessecarterMOOSE/moose,harterj/moose,sapitts/moose,bwspenc/moose,andrsd/moose