BUG: wrong bounding of sensitivity contituents in case of many control boxes (Fixes #1549)

When more than one volumetric B-Splines control boxes are present, the sensitivity constituents corresponding to the non-active design variables were not bounded(zeroed) correctly. The resultant sensitivities, used in the optimization, were bounded correctly, so this was more a bug pertaining to the output file of the sensitivities rather than a functional one.

src/optimisation/adjointOptimisation/adjoint/displacementMethod/displacementMethodvolumetricBSplinesMotionSolver/displacementMethodvolumetricBSplinesMotionSolver.C

@@ -5,8 +5,8 @@
     \\  /    A nd           | www.openfoam.com
      \\/     M anipulation  |
 -------------------------------------------------------------------------------
-    Copyright (C) 2007-2019 PCOpt/NTUA
-    Copyright (C) 2013-2019 FOSS GP
+    Copyright (C) 2007-2020 PCOpt/NTUA
+    Copyright (C) 2013-2020 FOSS GP
     Copyright (C) 2019 OpenCFD Ltd.
 -------------------------------------------------------------------------------
 License
@@ -108,7 +108,7 @@ void displacementMethodvolumetricBSplinesMotionSolver::boundControlField
     // control points movement. Safe since the motionSolver can only be an
     // volumetricBSplinesMotionSolver
     refCast<volumetricBSplinesMotionSolver>
-        (motionPtr_()).boundControlPointsMovement(controlField);
+        (motionPtr_()).boundControlPointMovement(controlField);
 }