refactor(core): Updates animate.enter queue comment for clarity

This updates the comment details about why we have to queue animations inside the animateEnter instructions and should help anyone needing to update this code in the future.

Author: thePunderWoman

packages/core/src/render3/instructions/animation.ts

@@ -77,8 +77,9 @@ export function ɵɵanimateEnter(value: string | Function): typeof ɵɵanimateEn
 
   initializeAnimationQueueScheduler(lView[INJECTOR]);
 
-  // TODO(thePunderWoman): it's unclear why we need to queue animations here, but without this,
-  // animating through host bindings fails
+  // We queue here for nodes that have enter animations and are not inside control flow. These elements
+  // are just a normal node in a template and would need to be queued here. Nodes that are inside control flow
+  // or otherwise enter the DOM post-render have enter animations queued in node_manipulation.ts.
   queueEnterAnimations(lView[INJECTOR], getLViewEnterAnimations(lView));
 
   return ɵɵanimateEnter; // For chaining
@@ -202,8 +203,9 @@ export function ɵɵanimateEnterListener(value: AnimationFunction): typeof ɵɵa
 
   initializeAnimationQueueScheduler(lView[INJECTOR]);
 
-  // TODO(thePunderWoman): it's unclear why we need to queue animations here, but without this,
-  // animating through host bindings fails
+  // We queue here for nodes that have enter animations and are not inside control flow. These elements
+  // are just a normal node in a template and would need to be queued here. Nodes that are inside control flow
+  // or otherwise enter the DOM post-render have enter animations queued in node_manipulation.ts.
   queueEnterAnimations(lView[INJECTOR], getLViewEnterAnimations(lView));
 
   return ɵɵanimateEnterListener;