enhancement(component examples): modernize state in docs/StackBlitz

[michael-small]

Documentation Feedback

See edit state for the original scope of this issue. Old scope/proposal: blanket change to accommodate some documentation examples having potential change detection issues. New scope: modernize remaining edge cases in documentation examples of components and CDK that could use signals to guarantee clean CD.

Progress

See linked PRs that have updated various examples to use signals. As of this edit where I am re-vamping the copy of this issue, there is a few core components documentation examples left, and then I will move onto the CDK.

My notes for outstanding changes/branches: https://gist.github.com/msmallest/f77adb004b9e88c49b3a248bab90a26a?permalink_comment_id=6237249

[msmallest]

I opened a PR for providing zone and another PR for adding Eager to Autocomplete examples. I will refrain from more PRs until I get approval, or given whatever strategy would make most sense.

Additionally, here is a branch where I combined the branch for providing zone with a oneoff addition of Eager to my table http example: main...msmallest:components:temp-example-of-zone-and-eager-combined-for-issue

[michael-small]

Ongoing notes going down the line checking off components if all their examples are zoneless+OnPush defaults ready, whether already or with a StackBlitz fork I make. As of posting this comment, I am just doing components fewest and easiest examples. Plenty are just fine as-is, but it is the more featured components with state that concern me. Something like the tables page or a form element are going to be the most interesting.

https://gist.github.com/michael-small/3b04460a8e9bcb114cf0aeb05f447b91