Allow MA0196 inheritdoc on constructors matching base signatures

[meziantou]

MA0196 was reporting <inheritdoc /> on constructors even in cases where constructor documentation is effectively inherited from a base constructor with the same signature. This created noise compared to the behavior users see in Visual Studio.

This change updates MA0196 to treat constructors as inheriting members when their signature matches a constructor on the base type.

What changed

• Updated InheritdocShouldBeUsedOnInheritingMemberAnalyzer to allow constructor <inheritdoc /> when a base constructor has the same signature.
• Signature matching is semantic and checks parameter count, parameter types, ref kind, and params shape.
• Kept diagnostics for constructors that do not match any base constructor signature.
• Added test coverage for matching and non-matching constructor signatures, including parameterless constructors.
• Updated docs/Rules/MA0196.md to document the constructor behavior and include an example.

Validation

• Ran targeted MA0196 analyzer tests on default Roslyn and on roslyn4.2 and roslyn4.14.
• Regenerated documentation with dotnet run --project src/DocumentationGenerator.

Fix #1145