Enable unsafe code refactoring creates unnecessarily complex projects

[sharwell]

Version Used: 16.6 Preview 4

Steps to Reproduce:

1. Create a CPS project
2. Write code with the unsafe modifier
3. Apply the code fix to enable unsafe code in the project

Expected Behavior:

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

  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
  </PropertyGroup>

</Project>

Actual Behavior:

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

  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
  </PropertyGroup>

</Project>

⚠️ Make sure to enable the CPSProject_GeneralPropertyGroupUpdated integration test as part of resolving this issue.

[sharwell]

@jmarolf is this a project system bug?