Fix to model scaling that was not resulting in the subject (target) mass being respected (matched) when preserve mass properties was unchecked. Turns out that the logic was OK and the bug was caused by updating the body mass properties but not recreating the system and state, so when the total mass was being queried, it was still the old mass that was in the system. Using the scaled model directly via scripting would also lead to a mismatched state-system with the model.

The remedy was to initSystem on the model after any changes in the model. There were a few places.
I don't understand the logic of the scale main creating the system and passing in a state to the Tool. This is antithetical to the idea of Tools just being the staging area to load the model(s) settings and doing the hookup to the necessary Solvers and Modelers.  The ModelScaler would make a good example of a Modeler if it didn't take a state and then expect that state to be valid after changing the model.

I took the liberty of removing the state as an input argument to the main processing methods ModelScaler and ModelPlacer. I have a suspicion that this will break functionality that GUI was expecting, but unfortunately it was wrong anyway. We will have to rethink why the GUI was passing in a state. Especially one that was not const!
Merge branch 'master' into FixToModelMassScaling
Remove state argument from processModel() method calls in Java and Python/OpenSimContext.cpp
Update typos in comments and remove commented out lines.
Also untabify files.
Merge pull request #230 from opensim-org/FixToModelMassScaling

Addresses model mass scaling issue, which fixes #223
Add comments to test case.
Merge branch 'master' of https://github.com/opensim-org/opensim-core into iterator

Conflicts:
	OpenSim/Simulation/Model/Model.cpp