Propose to de-escalate double constructor declaration warning to info

[jurgenvinju]

Describe the bug

It is normal to have constructors with the same names but for different types in the same namespace. This warning makes it seem like a problem, but the typechecker itself is the way out of the problem because it will ask for a disambiguation at the call site.

I really do not want to rename these constructors since this is the same concept modeled in another tier of language model. One is the syntax of the type names (Type), and the other is their symbolic representation for computing with types (TypeSymbol).

If we de-escalate this to an "info" message we get the same information but without the urge to have to fix it.

[PaulKlint]

Yes makes sense, downgraded to info and made message more helpful.

[PaulKlint]

Done