fix Component Governance file can't find warning

[qiutongMS]

This PR fixes Component Governance warnings that were occurring due to inconsistent capitalization of the configuration parameter across the build system. The warnings showed paths like:

##[warning]Project path C:\__w\1\s\eng\PackageReference\IXP\IXP.TransportPackage.PackageReference.csproj specified by D:\a\_work\1\s\obj\release\x86\IXP.TransportPackage.PackageReference\project.assets.json does not exist.
##[warning]Project output path C:\__w\1\s\obj\Release\x86\IXP.TransportPackage.PackageReference\ specified by D:\a\_work\1\s\obj\release\x86\IXP.TransportPackage.PackageReference\project.assets.json does not exist.

Root Cause

The issue was caused by inconsistent configuration parameter casing:

• BuildAll.ps1 defaults to "Release" (uppercase R)
• Azure DevOps pipelines explicitly passed "release" (lowercase r)
• build-nupkg.ps1 defaulted to "release" (lowercase r)

This caused project.assets.json files to reference different obj directory paths (obj\Release\ vs obj\release\), creating Component Governance warnings about non-existent paths.

[qiutongMS]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[qiutongMS]

/azp run