[Blazor] Performance - Change detection - set parameters only

[hakenr]

1. When I think back to what wasn’t entirely clear to me and I had to test and look up in the source code - the whole condition for primitive types in change detection applies to the parameters used (set) in a specific place, not to the component having non-primitive parameters.
2. Starting net9 EventCallbacks are included in change detection.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/performance.md	ASP.NET Core Blazor performance best practices

[guardrex]

Looks good except for a couple of NIT suggestions.

One more thing ... can you move the lead-in sentence outside of the bullet list?

To prevent rendering recursion into a particular subtree, use either of the following approaches:

Move that ☝️ to one line above the first moniker-range.

[hakenr]

All your suggestions should be resolved now.

[guardrex]

Excellent!