Update QuantConnect.pythonnet to 2.0.63

[jhonabreul]

Description

Bumps the QuantConnect.pythonnet package reference from 2.0.61 to 2.0.63 across all projects that consume it (11 .csproj files).

Refs: QuantConnect/pythonnet#137, QuantConnect/pythonnet#138

Related Issue

N/A — routine dependency version bump.

Motivation and Context

Keeps the LEAN solution on the latest QuantConnect Python.NET runtime build, ensuring consistency with the foundation Docker image and picking up upstream pythonnet fixes.

2.0.63 (QuantConnect/pythonnet#138) fixes the PythonUtilTests.BothInheritedAndNonInheritedClassesWork(True) CI failure this PR hit at 2.0.62: a failed PyObject.TryAs/TryAsManagedObject conversion left the Python error indicator set on the thread, and with 2.0.62's thread-state pinning (QuantConnect/pythonnet#137) the stale error survived across Py.GIL scopes and was thrown by the next Python call on the same NUnit worker thread (ExtensionsTests.PyObjectTryConvertToNonDelegateFail leaked it; PythonUtilTests tripped over it). 2.0.63 makes failed Try-conversions clear the pending error.

Note: requires QuantConnect.pythonnet 2.0.63 to be published to NuGet (pending merge of QuantConnect/pythonnet#138) before CI can restore.

Requires Documentation Change

No.

How Has This Been Tested?

Version bump only — no source code changed. The updated package restores and builds via the standard solution build; existing CI (build + unit/regression suites) validates the runtime.

The 2.0.62 CI failure was reproduced locally (running Common.Util.ExtensionsTests + Common.Util.PythonUtilTests on a single NUnit worker) and verified fixed with the 2.0.63 build.

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>