[jhonabreul]

Description

Updates the QuantConnect.pythonnet package reference to 2.0.68 in the 11 csproj files that consume it.

2.0.68 ships four pythonnet changes:

• Fix deadlock when threads first resolve lazy Python members concurrently pythonnet#154: fixes a deadlock when two threads first resolve a lazy Python member (Decimal, datetime, tzinfo) concurrently.
• Show an overridden ToString() in the default repr of .NET objects pythonnet#156: the default repr() of a .NET object shows its overridden ToString(), so a list of Symbol prints the tickers instead of <QuantConnect.Symbol object at 0x...>.
• Report converter failure causes explicitly instead of through the error indicator pythonnet#157: converter failures (throwing implicit operators, deleted types) are reported explicitly instead of through the Python error indicator, so they no longer leak into unrelated calls, and key in obj on a throwing conversion raises TypeError instead of crashing the process.
• Add GitHub workflow to build and publish the NuGet package pythonnet#155: CI-only, adds the NuGet publish workflow.

Companions: QuantConnect/LeanCloud#1552, QuantConnect/LeanCloud.Services#279.

Related Issue

N/A

Motivation and Context

Keeps LEAN on the latest QuantConnect.pythonnet.

Requires Documentation Change

No

How Has This Been Tested?

Version bump only. Each change is covered by tests in its pythonnet PR.

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>