Add high-signal analyser warnings

Expand Objo Studio's live analyser with a focused set of warnings for common code-quality issues that are precise enough to be useful while avoiding broad style policing.

Proposed warnings:

• Exception subclass whose name does not include Exception.
• Interface redeclared on a subclass when it is already implemented by a superclass.
• Method, constructor, or event handler with too many parameters.
• Private or member constant declared but never referenced.
• Method complexity warning based on a combined metric for branching, loops, nesting, and large ElseIf chains.

These warnings should appear in the existing Errors & Warnings panel and be individually configurable in the analyser settings.