[geometry] fixed issue (found myself with testcase #buffer_mp2) where, in double precision, a false intersection point was inserted. This was a robustness issue, an inconsistent side-value in colinear-opposite handler of get_turn_info

svn path=/trunk/boost/geometry/; revision=83475