Fixed a bug where circle angle property resets to 0 after first element when applying warp to multiple elements

[ericfreese]

Instead of overwriting the circle.angle property with the calculated radian angle, the code should add a new property to keep the original angle property unaffected.

Not sure how it should be minified, so I'll leave that to you or someone else.

The code that triggered the bug for me:

  cssWarp({
    path: {
      radius: 60,
      angle: '180deg'
    },
    targets: '.someclass'
  });

The first target used the correct angle of 180deg, but following targets reverted to angle of 0 (or close to it), because the angle was rewritten in radians and then re-interpreted as degrees.