Fix detector component filepath custom overrides

[grvillic]

Context

A detector does not need to specify location where a component was found. Nevertheless, custom wrapper plugins can report additional locations if desired and that shouldn't be blocked.

In PR #648 a regression occurred while trying to address an experiments framework bug. We don't want to unsuspectingly record locations for experimental detectors before producing the final graph. We added a check to prevent experiments from overriding the graph, but this was partially incomplete, because we are clearing the file paths at the top of the method.

Solution

Use the same flag to verify if the component file paths should be updated and only clear the list when generating final graph.

[codecov]

Codecov Report

Attention: Patch coverage is 98.14815% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.6%. Comparing base (9408a0e) to head (16cf57a).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...GraphTranslation/DefaultGraphTranslationService.cs	80.0%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #1306   +/-   ##
=====================================
  Coverage   89.6%   89.6%           
=====================================
  Files        378     378           
  Lines      29907   29960   +53     
  Branches    1837    1840    +3     
=====================================
+ Hits       26808   26861   +53     
  Misses      2707    2707           
  Partials     392     392           

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂