[Tizen] Destroy removal visuals after idler

[Tizen] Destroy removal visuals after idler

This is a combination of 3 commits.

Revert "[Tizen] Keep reference when member callback excute"

Keep reference when member callback excute + Make NPatchData as RefObject

Some CallbackBase didn't hold the reference of itself.
So it was possible to call destructor of itself during it's
API was running.

It might makes some unknown issues. So let we keep reference
for some issue-comes known APIs : SvgVisual, NPatchData, and lottie

It future, we should discard visuals rather than delate it directly.

Destroy removal visuals after idler

There was some bug when visual destructor called during
it's emit ResourceReady.

To avoid this case, Let we keep visuals more long term,
and Discard + Destroy after some idler called.

To avoid multiple Idler callback register,
let we make that idler callback in VisualFactory.

Change-Id: I4156f1af3cf40ffb30235dc9e6c55f9c7633f21d