Binary report publishing should not be source-build-specific

[mthalman]

The test for detecting binaries is executed for both Microsoft and source-only builds. But the publishing of the report to be made available as a pipeline artifact is only done for source-only builds: https://github.com/dotnet/dotnet/blob/52ea5b7695e7a1b6e960ba1faa0ef316f2b3f872/eng/PublishSourceBuild.props#L145-L154. This publishing should also be done for Microsoft builds.

[ellahathaway]

This is intentional. The internal source-built validation does not happen in the build legs, whereas the msft validation does happen in the build legs. As a result, the binary report has to be published as a build artifact for source-only builds so that it can be consumed in the subsequent validation leg.

That said, I understand that the publishing inconsistent. Maybe we 1) publish the artifact for msft and source-only builds (this will be necessary if the msft validation moves to new legs), 2) only publish the artifact for source-only internal builds.

Note that the artifact is always published as a log artifact, it's just inconsistent for the build artifacts.