Add exception interpreters for Python ModuleNotFoundError and multiple inheritance TypeError

[jhonabreul]

Description

Two common Python algorithm initialization failures currently surface through the generic PythonExceptionInterpreter with no guidance on how to fix them:

AlgorithmPythonWrapper(): No module named 'MathNet'

AlgorithmPythonWrapper(): cannot use multiple inheritance with managed classes
  at <module>
    class QuarterDailyMomentum(QCAlgorithm, LogMixin):

Cause: importing a C# namespace whose assembly has not been loaded into the CLR raises ModuleNotFoundError, and defining a Python class with a managed class plus another base raises TypeError — neither had a specialized interpreter.

The fix:

• ModuleNotFoundPythonExceptionInterpreter matches PythonExceptions whose Python type is ModuleNotFoundError and appends a short hint: install the package if it is a Python one; importing .NET assemblies is not supported, so use an equivalent Python package instead.
• MultipleInheritancePythonExceptionInterpreter matches the cannot use multiple inheritance with managed classes TypeError and recommends keeping the C# class as the only base, moving the other bases' members into helpers used via composition.
• Both run at Order = 0, taking precedence over the generic PythonExceptionInterpreter, and keep the parsed Python stack trace so the failing line is still shown.
• Messages are intentionally one sentence of advice each to keep runtime error output short.

Related Issue

N/A

Motivation and Context

Actionable one-line hints let users (and LLM assistants reading the error) fix these failures without external help, while keeping the error message short.

Requires Documentation Change

No.

How Has This Been Tested?

• New ModuleNotFoundPythonExceptionInterpreterTests and MultipleInheritancePythonExceptionInterpreterTests: CanInterpret type matrix, Interpret mismatch behavior, and interpreted-message content through StackExceptionInterpreter.CreateFromAssemblies.
• New module_not_found / multiple_inheritance trigger methods in Test_PythonExceptionInterpreter.py.
• Full QuantConnect.Tests.Common.Exceptions suite: 125 passed, 0 failed.
• Verified the final messages end-to-end through AlgorithmPythonWrapper construction and full Launcher backtest runs of reproduction algorithms for both failure modes.

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>