The source-built SDK that is published as an artifact of a VMR build uses the same filename that is produced by the output of the sdk repo. In the case of stable versioning, this can lead to collisions in the storage account because it doesn't have any other part of the path that produces uniqueness. This differs from the source-built artifacts tarball, for example, which always uses a non-stable version in its filename.

This is fixed by adding a symlink file which references the original SDK tarball. The symlink uses the non-stable version filename. The metadata constructed for publishing then references the symlink file so that the publishing manifest file is defined as we want. This allows the SDK tarball that is produced by the VMR built to still be named as it has always been but with the added benefit of always using a non-stable version filename when actually publishing that file.

Review the changes by viewing each commit. The first commit does a small refactor by moving logic source-build-specific logic from Publishing.props to PublishSourceBuild.props. The rest is actual changes to fix the issue.