fix: Aggressive Reporting support in resolveToTestingLibraryFn

[y-hsgw]

Checks

• I have read the contributing guidelines.

Changes

• Fix matching logic for testing-library/utils-module in resolveToTestingLibraryFn

Context

Fixes #1038

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.46%. Comparing base (7812dae) to head (b6b14fe).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1043      +/-   ##
==========================================
- Coverage   96.48%   96.46%   -0.03%     
==========================================
  Files          49       50       +1     
  Lines        2678     2686       +8     
  Branches     1110     1106       -4     
==========================================
+ Hits         2584     2591       +7     
- Misses         94       95       +1     

☔ 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.

[Belco90]

There are several utils related to detect Testing Library modules in lib/create-testing-library-rule/detect-testing-library-utils.ts, perhaps we can reuse something here?

If not, we probably need to combine that module with this one at some point.

[y-hsgw]

You're absolutely right.
Taking this opportunity, I implemented a function（isTestingLibraryModule）to detect Testing Library modules.