Consider removing `detect-binaries.sh` script

[ellahathaway]

See dotnet/dotnet#553 (comment)

We should consider removing the stand-alone detect-binaries.sh script now that its detection functionality has been integrated into the build process. This change would simplify the workflow, improve speed, and enhance cross-platform support. The original script was created to help distro maintainers detect and remove binaries, but if that support is no longer needed via script functionality, we should remove the script and integrate the cleaning of binaries into the source-build build process as well.

[MichaelSimons]

[Triage] We should preserve the logic to remove binaries with the prep script which depends on detect-binaries.sh.

[ViktorHofer]

I don't understand why we can't replace the detect-binaries.sh script with an msbuild project instead: init-detect-binaries.proj. detect-binaries.sh already depends on an SDK to invoke dotnet run BinaryToolKit.csproj. Why can't we do dotnet msbuild init-detect-binaries.proj instead of sh detect-binaries.sh?

The current indirection is causing this issue: #5223

[MichaelSimons]

I don't understand why we can't replace the detect-binaries.sh script with an msbuild project instead: init-detect-binaries.proj. detect-binaries.sh already depends on an SDK to invoke dotnet run BinaryToolKit.csproj. Why can't we do dotnet msbuild init-detect-binaries.proj instead of sh detect-binaries.sh?

There is nothing technically preventing this refactoring. This issue was closed based on a lack of business justification for the refactoring. #5223 may provide this.