Replace Ellipse-based Ripple with Composition API

[maxkatz6]

Just an experiment, which potentially can be a nice improvement for low-end devices.
Currently, Ripple effect is implemented with an Ellipse shape animated with multiple transitions on the UI thread.
This PR rewrites this effect to be executed on the Render thread, and UI thread is responsible for starting animation and triggering second step (fading out opacity).

On my local machine with Debug build (to make it slower), I can see animation working way better in navigation buttons, but not really different on normal buttons. It must be because navigation buttons are loading new pages on click, blocking UI thread for a moment - that's where Render thread animations work better, as they can be rendered and computed in parallel.

Breaking changes:

• Ripple class is not an Ellipse, and is a static class that allows some Easing and Duration customizations (like it was before).
• There is no canvas in the default template (minor)

I also moved default properties from setters to the styled property definitions. Ideally, I would also avoid "^:not(.no-transitions)" selector, as it's going to be applied on each button, adding some styling overhead. But that's not in the scope of this PR.

Math in this PR is a bit off, and the ripple effect doesn't fill whole parent. I guess the old code had Margin transition for that, but I haven't dive too deep.

[maxkatz6]

Before:

demo1.mp4

After:

demo2.mp4

[JanTamis]

wow really nice!

[SKProCH]

Look fine for me, but i should investigate how to make it more simular to current implementation.