Description

Update all CSProj files to the new format

Includes:

• Migration from packages.config to PackageReference -> Reduces work of managing packages to a single line per package in proj file.
• Migration to project sdk Microsoft.NET.Sdk -> Moves us to .Net standard proj format, allowing us to target more frameworks in the future as well as cleans up project files significantly. This is the largest change by far as it impacts the entire structure of the proj files. Including removal of a lot of default settings to reduce clutter.
• Compile globbing -> instead of relying on compile include statements all files in the project are by default compiled, to not compile we must use Compile Remove
• Reduction of certain build settings into a overhead default that utilizes dynamic vars such as $(Configuration) to further reduce clutter.
• Use $(NugetPackageRoot) variable instead of relative pathing for specific dll finds. -> With the change to packages, the storage is no longer in ./packages, so we needed to have a dynamic path variable to address this.
• Test project now includes Microsoft.NET.Test.Sdk allowing for dotnet test as well as supporting testing in VS16 project (new version this PR moves us too)
• Open some internal test classes to public for composer use (There was issues in linux testing regarding accessing these classes)

Related Issue

Closes #1686
Related to #452

Motivation and Context

To move forward with supporting dotnet core we need to update our project files to the new .net standards.

Requires Documentation Change

N/A

How Has This Been Tested?

• dotnet build works
• msbuild works
• All regressions pass locally on Windows 10
• Travis test set runs successfully in Docker container and on Ubuntu 20.04
• C# and Py Live trading tested in cloud and locally*
• C# and Py Backtesting tested in cloud and locally*
• C# and Py Research tested in cloud and locally*
• C# and Py Debugging tested in cloud and locally*

*locally refers to windows 10 environment and cloud refers to QuantConnect.com

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>