Fix dotnet detector for exes / newer version not on path

[ericstj]

We weren't handling EXEs correctly - simply missed this case.

When a global.json mentions a version that doesn't exist on the path, the dotnet --version command will fail, and the commandLineInvocationService will throw InvalidOperationException since it cannot distinguish this failure from a missing command. Catch this exception and treat it like a failure so we fallback to parsing global.json.

[codecov]

Codecov Report

Attention: Patch coverage is 96.92308% with 4 lines in your changes missing coverage. Please review.

Project coverage is 89.5%. Comparing base (255e011) to head (ebfba5d).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...ection.Detectors/dotnet/DotNetComponentDetector.cs	88.8%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@          Coverage Diff           @@
##            main   #1367    +/-   ##
======================================
  Coverage   89.5%   89.5%            
======================================
  Files        402     402            
  Lines      31480   31599   +119     
  Branches    1928    1944    +16     
======================================
+ Hits       28186   28302   +116     
- Misses      2879    2881     +2     
- Partials     415     416     +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.

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