test(wizard): use signals and detectChanges

[ljanner]

Resolves #1528

---

• I confirm that this MR follows the contribution guidelines.

[gemini-code-assist]

Code Review

This pull request refactors the tests for the SiWizardComponent to align with modern Angular testing practices. The changes involve migrating from class properties to signal-based inputs in the test host component and replacing the custom runOnPushChangeDetection helper with the standard fixture.componentRef.setInput() and fixture.detectChanges() APIs. This simplifies the test code, improves readability, and removes unnecessary asynchronous operations from several tests, making them more efficient. The changes are well-executed and represent a good improvement to the test suite.

[Copilot]

Pull request overview

Updates the SiWizardComponent unit tests to stop using the runOnPushChangeDetection() helper and instead drive updates via signal-based inputs with fixture.componentRef.setInput(...) + fixture.detectChanges(), aligning with the approach requested in issue #1528.

Changes:

• Removed usage of runOnPushChangeDetection() from the wizard spec.
• Switched host bindings for hideNavigation and inlineNavigation to signal inputs (input(...)) and updated tests to set them via componentRef.setInput(...).
• Converted affected async tests/hooks to synchronous ones where no async stabilization is needed.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Documentation.
Examples.
Playwright report.

Coverage Reports:

• element-ng
• element-translate-ng

[spliffone]

It isn't necessary to use input for the HostComponent, can we use simple signals instead?

[ljanner]

It isn't necessary to use input for the HostComponent, can we use simple signals instead?

Refactored to use simple signals 👍

[github-actions]