Combine signed assets publishing in one stage

[MilenaHristova]

The Stage-DotNet pipeline publishes signed assets in 2 separate stages - Publish Post-Signing Assets and Published Signed Assets. Both stages download the same artifacts, but publish them to different storage accounts

• [ ] Investigate the differences between the 2 stages and why they were done separately
• [ ] Double-check that they download and publish the same artifacts
• [ ] Combine them into a single stage to ideally publish everything using the same tool

[MilenaHristova]

I looked at the jobs and made this table of what each job is downloading

Publish Post-Signed Assets	Publish Signed Assets	Publish Signed Packages	Published Signed Symbols	Publish VS NuPkgs
signed (51,791.7 MB)	signed/shipping/assets/, signed/nonshipping/assets/ (41,419.7 MB)	signed/shipping/packages/*/*.nupkg, signed/nonshipping/packages/*/*.nupkg (10,372.0 MB)	signed/shipping/assets/symbols/., signed/shipping/assets/pdbs/. (5,948.9 MB)	signed/*/VS.Redist.Common.*.nupkg (1,804.1 MB) ; signed/./VS.Tools.Net.*.nupkg (1,020.7 MB)
notarizedPackages **.pkg, **.pkg.sha512,**.tar.gz, **.tar.gz.sha512 (2,090.9 MB)	notarizedPackages **.pkg, **.pkg.sha512, **.tar.gz, **.tar.gz.sha512 (2,090.9 MB)	-	-	-
linux-signed 4,443.0 MB	linux-signed (4,443.0 MB)	-	-	-
manifests\manifest.json (2.2 MB)	manifests\manifest.json (2.2 MB)	manifests\manifest.json (2.2 MB)	-	-
config.json	config.json	config.json	-	-

The Publish Signed Assets stage which includes Publish Signed Assets, Publish Signed Packages, Published Signed Symbols, Publish VS NuPkgs downloads the same assets as the Publish Post-Signed Assets stage