Use "new" symbol package format when publishing

[billbogaiv]

🔧 Enhancement Request

For symbol deployments to NuGet, it no longer supports the *.symbols.nupkg format—versus the "newer" *.snupkg-format.

To accommodate this requirement, we can either wait until Cake publishes the update that includes cake-build/cake#3331 or manually modify the cake-scripts to include ArgumentCustomization re;

build-scripts/build-net5.cake

Lines 325 to 332 in 2a6fe3f

	DotNetCorePack(clientProjectPath, new DotNetCorePackSettings
	{
	Configuration = configuration,
	MSBuildSettings = new DotNetCoreMSBuildSettings().SetVersion(packageVersion),
	NoBuild = true,
	OutputDirectory = artifactsDir,
	IncludeSymbols = true
	});

Sample update

DotNetCorePack(clientProjectPath, new DotNetCorePackSettings
{
    Configuration = configuration,
    MSBuildSettings = new DotNetCoreMSBuildSettings().SetVersion(packageVersion),
    NoBuild = true,
    OutputDirectory = artifactsDir,
    IncludeSymbols = true,

    // New code...
    ArgumentCustomization = x => x.Append("-p:SymbolPackageFormat=snupkg")
});

Also ref. https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg

Who is asking for the feature?

@billbogaiv

What business problem is this hoping to solve?

Improve debug experience when using packages—we'll be able to see "source-code" variable names (versus compiled-names), etc.