househeeping: resolve broken CI infrastructure

[ghuntley]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Housekeeping

What is the current behavior? (You can also link to an open issue here)

Our build is currently broken

What is the new behavior (if this is a feature change)?

Moves all of our pinned dependencies to a consistent version so that we may fix GitVersion. After this PR is merged the build will be green and we can proceed with motions of release.

What might this PR break?

Nothing but we will be unable to test the release workflow until develop is merged into master.

Other information:

These tasks are outstanding before this PR can be merged

• Upgrade Cake.FileHelpers to Cake.Core 0.22.0 (inc PR'ing upstream ecosystem if needed

• Upgrade Cake.Coveralls to Cake.Core 0.22.0 (inc PR'ing upstream ecosystem if needed

• Upgrade Cake.PinNuGetDependency to Cake.Core 0.22.0 (inc PR'ing upstream ecosystem if needed

• Upgrade Cake.Powershell to to Cake.Core 0.22.0 (inc PR'ing upstream ecosystem if needed

• Resolve GitVersion errors (run cake at diagnostic logging to see specifics of the GitVersion stacktrace.)

• Upgrade these if needed:

#tool "nuget:?package=GitReleaseManager&version=0.6.0"
#tool "nuget:?package=GitVersion.CommandLine&version=3.6.5"
#tool "nuget:?package=coveralls.io&version=1.3.4"
#tool "nuget:?package=OpenCover&version=4.6.519"
#tool "nuget:?package=ReportGenerator&version=2.5.11"
#tool "nuget:?package=vswhere&version=2.1.4"

[ghuntley]

Blocked by cake-contrib/Cake.PinNuGetDependency#3

[ghuntley]

Related issue @ NuGet/Home#5894

[ghuntley]

Related issue at

[ghuntley]

Amongst other things, we had to do some msbuild hacks for WPF. See related issue @ NuGet/Home#5894