test: add util to type-safely set signal inputs

[davidlj95]

After using input signals in most components around, now to set those inputs the componentRef.setInput function is used.

However, that function is not type-safe. So:

• Name may be wrong: one can make a typo and nothing would happen
• Value type may be wrong
• Refactoring: if at some point the name of the component input property to set changes, it would need a manual update

Introducing here a set of type-safe APIs that use the main API under the hood. To allow easy refactoring and type checks for the name and value type to set.

[davidlj95]

• test: add util to type-safely set signal inputs #877 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.99%. Comparing base (303a4bc) to head (f7c2cae).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #877      +/-   ##
==========================================
+ Coverage   95.95%   95.99%   +0.03%     
==========================================
  Files         123      124       +1     
  Lines         618      624       +6     
  Branches       70       70              
==========================================
+ Hits          593      599       +6     
  Misses         19       19              
  Partials        6        6              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

🚀 This pull request is included in v2.63.2. See v2.63.2 for release notes.