Fixed release failure

[RushabhBhansali]

Summary

Previous release (2.0.1) failed during publishing step (failure). This is a fix for it.

Rootcause:
after .net6 migration the default publishing step was generating multiple asset files in the ./bin folder. This was causing failure in Publish CLI tool step, since its only expecting single file under ./bin.

due to .net6 migration , it was required that we add `-p:IncludeAllContentForSelfExtract=true (source).

Testing:

• locally ran dotnet publish --configuration Release --output ./bin --self-contained --runtime win-x64 -p:PublishSingleFile=true -p:IncludeAllContentForSelfExtract=true -p:DebugType=None -p:PublishTrimmed=false ./src/Microsoft.ComponentDetection command to validate that only single file is generated.
• validated that generted .exe file is able to run properly and scan components on windows platform.

[JamieMagee]

Third time's the charm!

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