Fixed TimelineLite/Max issue with scheduling an append of a child that's already in the timeline

Now when a child is appended/inserted into a TimelineLite/Max, it
checks to see if it's already a child and if so, removes it before
calculating the position. Previously if you tried appending a child
that's already in the timeline, it could contaminate the duration.