fix(core): run afterRender callbacks outside of the Angular zone

[devknoll]

afterRender should run outside of the Angular zone so that it does not trigger further CD cycles

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Callbacks are executed in the Angular zone, causing patched APIs like setTimeout to trigger subsequent change detection cycles, and further afterRender callbacks.

Issue Number: #51343

What is the new behavior?

Callbacks are always executed outside of the Angular zone, preventing accidental infinite render loops.

Does this PR introduce a breaking change?

• Yes
• No

afterRender is in developer preview, and so this is not considered a breaking change.

Other information

Closes #51343

[devknoll]

cc @kara

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     2 pending code reviews

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[alxhub]

@devknoll can you change the commit to fix, not feat? Our merge tooling will reject merging a feat commit to the 16.2.x branch.

[jessicajaniuk]

@devknoll I see this has action: presubmit, but this is showing as passing. Is another presubmit needed? Or a TGP?

[kara]

@jessicajaniuk oh, my mistake. I added the label bc I didn't see it already ran. Will remove.

[jessicajaniuk]

@devknoll I'm going to update this to target: minor, but we'll need a patch PR to get it into 16.2.x. Please create that at your leisure.

[jessicajaniuk]

This PR was merged into the repository by commit 3a19d6b.

[angular-automatic-lock-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.}