fix(pip): added working dir to python setup.py exec

[edena-legit]

Some setup.py files might load data from the file's working dir, such as the README.md file. Currently, when parsing a setup.py file and executing it, the Python command is executed without specifying the working dir.

[cobya]

Thanks for the contribution. In order for us to be able to accept it, please review the CLA mentioned above @edena-legit

[edena-legit]

@microsoft-github-policy-service agree company="Legit Security"

[edena-legit]

@melotic anything else?

[edena-legit]

@cobya

[codecov]

Codecov Report

Attention: Patch coverage is 92.85714% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 75.0%. Comparing base (2de3cc0) to head (5e0ad0d).
Report is 11 commits behind head on main.

Files	Patch %	Lines
...ft.ComponentDetection.Common/PathUtilityService.cs	0.0%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #914     +/-   ##
=======================================
- Coverage   75.6%   75.0%   -0.7%     
=======================================
  Files        239     239             
  Lines      10821   10833     +12     
  Branches    1086    1087      +1     
=======================================
- Hits        8188    8125     -63     
- Misses      2321    2392     +71     
- Partials     312     316      +4     

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

[cobya]

@edena-legit looks like the test run is failing with NullReferenceException: Object reference not set to an instance of an object. if you could please take a look

[edena-legit]

@edena-legit looks like the test run is failing with NullReferenceException: Object reference not set to an instance of an object. if you could please take a look

@cobya thats weird as it seems it only occurs in windows build, it seems like runs after were ok..?

[cobya]

#1129 has now handled this 😄