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]

@jessicajaniuk @alxhub

[jessicajaniuk]

This PR was merged into the repository by commit 0c7c852.

[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.}