feat(component): use global render strategy in zone-less mode

[markostanimirovic]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngrx/platform/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Closes #3342

What is the new behavior?

@ngrx/component uses a global rendering strategy in zone-less mode.

Does this PR introduce a breaking change?

[x] Yes
[ ] No

BREAKING CHANGES:

The native local rendering strategy is replaced by global in zone-less mode for better performance.

BEFORE:

The change detection is triggered via `changeDetectorRef.detectChanges` in zone-less mode.

AFTER:

The change detection is triggered via `ɵmarkDirty` in zone-less mode.

[netlify]

✅ Deploy Preview for ngrx-io ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	737f129
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/625767499f77770008d5ae28
😎 Deploy Preview	https://deploy-preview-3379--ngrx-io.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[LayZeeDK]

@markostanimirovic
How confident are you that ɵmarkDirty won't suddenly be removed or changed? It's a function internal to Angular and intentionally not part of its public API surface.

[markostanimirovic]

@LayZeeDK

The previous way of triggering CD in zone-less mode via cdr.detectChanges without coalescing was inefficient and it had to be changed. Because we use the "global" rendering strategy in zone-full mode, we agreed to use the same strategy in zone-less mode.

I chose ɵmarkDirty because it already implements what we need in the zone-less mode for the "global" rendering strategy - it marks the passed component as dirty, schedules a tick, and coalesces multiple ɵmarkDirty calls into a single CD run.

I'm aware that ɵmarkDirty can be changed/removed at any moment. However, it has been part of the "ɵpublic" API for more than 2 years. If Angular team decides to remove it, we'll implement a custom solution for scheduling/coalescing tick calls in zone-less mode.

[LayZeeDK]

@markostanimirovic
angular/angular#46709