317 non-baselined VMR comparison issues

[ellahathaway]

There are 317 non-baselined VMR comparison issues that should be investigated and baselined, if necessary.

Link to build

[mmitche]

Here's what I see:

• A ton of symbol packages that are classified as non-shipping (probably via their parent package designation) in isolated builds, and shipping in the VMR
• A few cases that look like they're caused by SDK updates
• A couple cases that need baselining.

[wtgodbe]

• dotnet-suggest from command-line-api is a missing shipping asset in the VMR - expected?
• Microsoft.DotNet.ApiDiff.Tests from dotnet/sdk is a missing nonshipping asset - seems like we can baseline this one
• Lots of misclassified symbol packages w.r.t. shipping/nonshipping - How have we dealt with these before?
• The aspnetcore VS.Redist packages are marked shipping instead of shipping - may have already been fixed
  • Fixed by Split up setting NonShipping and DotNetReleaseShipping ManifestArtifactData dotnet#761

[mmitche]

Lots of misclassified symbol packages w.r.t. shipping/nonshipping - How have we dealt with these before?

I think this is a publish.proj issue...My hunch was that these are all cases where Arcade is auto-generating symbol packages, and incorrectly classifying them.

[mmitche]

That said, it doesn't actually impact our shipping...the symbol packages get unpacked and indexed no matter what, and they end up in the same spot in storage either way.