Release handling

[masojus]

Debugging symbols and Debug vs Release. We should make sure to push release version to NuGet and push release symbols to symbolsource.org. We should also use something else, like myget or VSTS to push debug versions for our own purposes or for select clients who need them for something...and also push debug symbols to symbolsource.org.

It's likely very little will change in the repo and is to just make sure we lock down this process and check all the boxes each time we push a release in the future. Mostly will just need to make sure to use the correct compiler flags and nuget.exe flags at release time.

[masojus]

As part of finalizing our release strategy for the new .NET Standard-based binary, we should change the name of the project (or at least the DLL that is produced) because right now it's Keen.NetStandard.dll which seems a little weird for the .NET Framework 4.5 output from the multi-targeted project. Ideally it'll eventually just be Keen.dll in both cases.

[masojus]

Name change and .nupkg creation parts are in review. The part about releasing symbols and a debug release flow are not yet planned.

[masojus]

The new project structure is in place and the script to bump the version and pack the .nupkg has been updated. Renaming the dll is fixed in PR #136 with commit 55b8985. What remains is dealing with symbols and having a way to release Debug assets if/when necessary.