Accept integral floats for int params, hint overloads on bind failure (2.0.57)

[jhonabreul]

Two related improvements to method/constructor argument binding, plus a version bump.

1. Accept integral-valued floats for integer parameters; reject non-integral ones.

Passing a Python float where a .NET integer parameter was expected behaved inconsistently:

• Single-overload targets silently truncated any float (e.g. 5.5 → 5) via Converter.ToManaged.
• Overloaded targets rejected every float, including integral-valued ones (e.g. 5.0), with "No method matches given arguments", because the overload-disambiguation path did not treat float→int as a valid conversion. This broke calls like RangeConsolidator(period) in Lean when period was a float.

Both paths are now consistent: an integral-valued float (5.0) is accepted and converted for integer parameters, while a non-integral float (5.5) is rejected with a TypeError instead of being silently truncated.

• MethodBinder: treat integral Python floats as implicit-conversion candidates for integer parameters (enums excluded).
• Converter.ToPrimitive: reject non-integral Python floats targeting integer types so truncation never happens silently.
• Added a shared Type.IsInteger() helper in Util and used it in both places.

2. Hint the candidate overloads in the "No method matches" TypeError.

When binding failed, the error only reported the argument types that were passed, giving no clue what the method actually expected. The message now appends the candidate overload signature(s), using the snake_case names Python callers use (method names and parameter names; constructors keep the special .ctor token). This applies to every "no match" case, not just numeric conversions.

Single candidate — a method taking a single int, showing the snake_case method and parameter name:

No method matches given arguments for compute_scaled: (<class 'float'>). The expected signature is:
  compute_scaled(Int32 scale_factor)

Multiple candidates — an overloaded method, each candidate listed in snake_case:

No method matches given arguments for compute_range: (<class 'float'>). The following overloads are available:
  compute_range(Int32 value, Func[Int32, Int32] selector = None)
  compute_range(Int32 value, PyObject selector, PyObject other = None)

The Int32 parameter is now visible, hinting that an integer was expected. For Lean's RangeConsolidator(5.5) the two constructor overloads are likewise listed with snake_case parameters (e.g. volume_selector). Signatures are rendered readably (friendly type names, by-ref/nullable unwrapped, generics as Name[Arg1, Arg2], params marked, optional parameters shown with their default). The list is de-duplicated and capped at 10 with a "... and N more" suffix. The whole hint is best-effort and wrapped in a try/catch so it can never mask the original binding failure.

3. Version bump. QuantConnect.pythonnet <Version> bumped 2.0.56 → 2.0.57 (with the matching AssemblyVersion/AssemblyFileVersion in Properties/AssemblyInfo.cs).