Fix integration tests with DotNet component type

[grvillic]

Context

We recently promoted DotNet component detector. Out integration tests were broken but the PR wasn't blocked.

We need to revisit if we are disabling them due to non-deterministic detectors or something else, otherwise we should enforce those CI checks for PRs.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.6%. Comparing base (81e93c7) to head (578a6e4).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #1396   +/-   ##
=====================================
  Coverage   89.6%   89.6%           
=====================================
  Files        401     401           
  Lines      31820   31821    +1     
  Branches    1964    1964           
=====================================
+ Hits       28539   28540    +1     
  Misses      2863    2863           
  Partials     418     418           

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

[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 🙂