fix: skip optimize_save_restore_view for Animation handler_ops

[Brooooooklyn]

Angular's ngtsc keeps restoreView/resetView in animation callbacks even when the return value doesn't reference the view context (e.g., return "animate-in"). OXC was incorrectly removing these via optimize_save_restore_view, causing 37 ClickUp component mismatches.

---

Note

Medium Risk
Changes variable optimization behavior for animation callbacks, which can affect generated template JS and runtime view/context handling in embedded views. Risk is moderate because it alters codegen semantics for animations but is narrowly scoped and covered by new integration snapshots.

Overview
Aligns codegen with Angular’s ngtsc by skipping optimize_save_restore_view for CreateOp::Animation handler ops, preserving restoreView/resetView even when the animation callback returns a simple literal.

Adds integration coverage and snapshots for embedded-view (@if) animations (both with and without a companion (click) listener) to ensure getCurrentView and the appropriate restoreView/resetView calls remain in the output and _unnamed_ references don’t appear.

^{Written by Cursor Bugbot for commit 5070286. This will update automatically on new commits. Configure here.}