Fixes #912.

This refactors the error-handling for scaling introduced in #810.

The current usage of JPH::Shape::IsValidScale poses some problems in the context of Godot, since the tolerance of JPH::Shape::IsValidScale is (understandably) quite small, and Godot doesn't do any sort of automatic orthonormalization of its transforms, which means that it doesn't take many frames for something like the rotation of a CharacterBody3D to start messing with the orthogonality of its transforms, thereby resulting in weird scaling and potentially causing JPH::Shape::IsValidScale to fail.

The technically correct resolution to this would of course be for the user to just orthonormalize its transforms, or for this extension to disregard scaling completely (like Godot Physics does), but given the friction involved with this, and the fact that some users have come to appreciate and rely on the (undocumented) support for scaling in this extension, a compromise has been reached instead.

This PR makes use of the newly introduced JPH::Shape::MakeScaleValid, which takes any arbitrary scaling and changes it just enough to be valid for the given shape. This means that we can make sure that Jolt always receives a correct scaling, but better yet we can also check to see how different this new valid scaling is from the one we put in, and emit an error based on a tolerance that we define ourselves.

So this effectively raises the tolerance from 0.0001-ish to 0.01. This will make sure that clearly incorrect scaling, such as deliberately scaling a capsule or sphere non-uniformly, will emit errors, but scaling as a result of accumulative precision errors are only reported if they're really bad.

Note that the correction of the scale (i.e. JPH::Shape::MakeScaleValid) happens regardless of build, whereas the error-reporting only happens in editor/debug builds.