Add configuration condition to VS csproj references ItemGroup

[cicanci]

What does this PR do?

Consider the following premake5.lua script line:

links { "bin/%{cfg.platform}/%{cfg.buildcfg}/MyLib.Sharp.dll" }

If you have more than one optimizations it will only consider the first one found. So, for example, if you have Debug and Release optimizations, the only DLL linked will be the Debug one, resulting in the following VS csproj configuration:

<ItemGroup>
  <Reference Include="MyLib.Sharp">
  <HintPath>..\..\bin\x64\Debug\MyLib.Sharp.dll</HintPath>
  </Reference>
</ItemGroup>

The changes in this PR make it possible to apply the same condition used in the <PropertyGroup> to the <ItemGroup> when linking a DLL in a VS csproj, resulting in the following VS csproj configuration (considering the previous example).

<ItemGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
  <Reference Include="MyLib.Sharp">
  <HintPath>..\..\bin\x64\Debug\MyLib.Sharp.dll</HintPath>
  </Reference>
</ItemGroup>
<ItemGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
  <Reference Include="MyLib.Sharp">
  <HintPath>..\..\bin\x64\Release\MyLib.Sharp.dll</HintPath>
  </Reference>
</ItemGroup>

How does this PR change Premake's behavior?

After this PR, any VS csproj that links a DLL will have the condition applied for each optimization defined. For example, if only Debug is used, the VS csproj will change from this:

<ItemGroup>
  <Reference Include="MyLib.Sharp">
  <HintPath>..\..\bin\x64\Debug\MyLib.Sharp.dll</HintPath>
  </Reference>
</ItemGroup>

To this:

<ItemGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
  <Reference Include="MyLib.Sharp">
  <HintPath>..\..\bin\x64\Debug\MyLib.Sharp.dll</HintPath>
  </Reference>
</ItemGroup>

Anything else we should know?

Not really, the changes are pretty straight forward.

Did you check all the boxes?

• Focus on a single fix or feature; remove any unrelated formatting or code changes
• Add unit tests showing fix or feature works; all tests pass
• Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
• Follow our coding conventions
• Minimize the number of commits
• Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

[nickclark2016]

Looks like we have tests failing here. Please investigate why these tests are failing, resolve the failures, and then add unit testing for the new piece of functionality.

[starkos]

Also, if you could squash your changes down to a single commit (you can force push to this branch to overwrite the previous commits) it will make it easier for us to merge it. Thanks!

[starkos]

Merged, thanks!