Suggest Super.Constructor(...) for mistaken superclass constructor calls

When a developer writes an incorrect superclass constructor call, the compiler should suggest the correct syntax, Super.Constructor(...).

For example, a constructor in StringMemoryTableColumn Inherits MemoryTableColumn might contain:

Super.MemoryTableColumn(parentCollection)

The current diagnostic, Type 'MemoryTableColumn' has no member 'MemoryTableColumn'., does not explain how to call the parent constructor. Add a helpful suggestion such as: To call the superclass constructor, use Super.Constructor(parentCollection).

This would make constructor chaining easier to discover and avoid the mistaken workaround of removing Super., which turns this one-argument expression into a cast rather than initialising the current instance.