refactor(navbar-vertical): explicitly define change detection strategy

[spliffone]

---

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

• charts-ng
• dashboards-ng
• element-ng
• element-translate-ng
• maps-ng
• native-charts-ng

[gemini-code-assist]

Code Review

This pull request updates several vertical and primary navbar components, along with their test host components, to use ChangeDetectionStrategy.OnPush to improve performance. The feedback suggests applying ChangeDetectionStrategy.OnPush to SiNavbarItemComponent as well, rather than explicitly setting it to Default, to maintain consistency with the rest of the changes.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Consider using ChangeDetectionStrategy.OnPush instead of ChangeDetectionStrategy.Default for SiNavbarItemComponent to align with the project's performance standards and other components in this PR.

Since SiNavbarItemComponent uses signal-based inputs (item, quickAction) and signal queries, it is well-suited for OnPush. If there are any legacy non-signal properties or mutable objects being passed, you can inject ChangeDetectorRef and call markForCheck() where appropriate (e.g., inside ngDoCheck()).

Suggested change

	changeDetection: ChangeDetectionStrategy.Default,
	changeDetection: ChangeDetectionStrategy.OnPush,

References

1. Set changeDetection: ChangeDetectionStrategy.OnPush in @component decorator. ^(link)