fix: auto-spy standalone inject() services (#9397)

[satanTime]

Summary

• auto-spy root-provided services resolved through standalone component inject() properties
• add focused regressions for inject(), constructor injection, and non-injected lookalike guards
• validate the issue against Angular 14 and scoped root coverage paths

Closes #9397

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9eed052) to head (4dff48e).

Additional details and impacted files

@@            Coverage Diff            @@
##              main    #13310   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          228       228           
  Lines         4168      4193   +25     
  Branches      1187      1192    +5     
=========================================
+ Hits          4168      4193   +25     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[satanTime]

Two review findings from a local pass.

[satanTime]

autoSpyStandaloneInjectProperties(...) runs only after the first fixture.detectChanges(). That means any inject()-backed service call made during ngOnInit, an effect triggered on the first render, or other first-pass lifecycle work still hits the original method and will never be counted by ngMocks.autoSpy(). The new regression test only exercises calls made after MockRender(), so this path stays uncovered.

[satanTime]

This helper is gated to components only via isNgDef(template, 'c'), but this render path also serves standalone directives, and the pipe wrapper case reaches the same area too. A standalone directive or pipe that uses inject() still appears to bypass auto-spy support, so either the guard needs widening or the narrower scope should be documented and covered explicitly.