Use SetGlobalProperty for updating $(Configuration)

[iskiselev]

Config property is not used for output path calculation when output path is overriden.

To reproduce it, use next project:

• Directory.Build.props:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <ProjPart Condition="'$(ProjPart)' == ''">$([MSBuild]::MakeRelative($(MSBuildThisFileDirectory),$(MSBuildProjectDirectory)))\$([System.IO.Path]::GetFileNameWithoutExtension($(MSBuildProjectFile)))</ProjPart>
    <OutputPath>..\..\output\bin\$(Configuration)\$(ProjPart)</OutputPath>
  </PropertyGroup>
</Project>

• Normal.csproj:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFrameworks>net8.0;net7.0</TargetFrameworks>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <JsonVersion>13.0.3</JsonVersion>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" Version="$(JsonVersion)" />
  </ItemGroup>

</Project>

• Program.cs

Console.WriteLine("Hello, World!");

Using SetGlobalProperty fixes the issue

[devmehtabd]

Thank you for putting forth this PR for us. But, after thorough investigation and understanding the use of Config Property, we feel that this block of code is not used by our Nuget Inspector to derive dependencies. We just use configuration to calculate the output paths but never use them further, so we would be putting forward a tech debt to remove this block of code for finding output paths and focus on getting BaseIntermediateOutputPath as described in this PR: #22.

Closing this PR.