fix(multiple): move afterRender calls back outside zone

[mmalerba]

Updates some calls to afterRender / afterNextRender to explicitly run outside the NgZone. These usages were originally explcitily run outside, but the explicit call was removed when they were updated to use the afterRender / afterNextRender function, since at the time it was automatically outside the zone. The semantics of afterRender / afterNextRendef have since changed so this is no longer true. Therefore this PR restores the original explicit run outside.

[mmalerba]

There are plans in the works to put afterNextRender back outside the zone, so this may wind up not being needed

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}