Errors on non-callable unions should be more specific

While working on #29011 I realized that the error we produce for unions of things which look callable but for which we cannot synthesize a signature for are lackluster. We report an error like:

Cannot use 'new' with an expression whose type lacks a call or construct signature.

when we could do better and say something like

Cannot use 'new' with an expression whose type lacks a call or construct signature. All members of union type {0} have call or construct signatures, but none are similar enough to resolve a call in a typesafe way.

which would make it far more clear what's going on in these scenarios.

Once #29011 is merged, the conditions can be even more specific, such as

Cannot use 'new' with an expression whose type lacks a call or construct signature. All members of union type {0} have call or construct signatures, but more than one has overloads, which prevents this call from being resolved in a typesafe way.

and

Cannot use 'new' with an expression whose type lacks a call or construct signature. All members of union type {0} have call or construct signatures, but more than one has type parameters, which prevents this call from being resolved in a typesafe way.

Bắt đầu từ chẩn đoán hiện có cho “Cannot use 'new' with an expression whose type lacks a call or construct signature” và xem xét các điều kiện liên quan được mô tả cùng với #29011. Hoàn tất khi các trường hợp union được báo cáo phân biệt được các chữ ký không thể tổng hợp, nhiều overload và nhiều tham số kiểu bằng các thông báo cụ thể hơn được hiển thị.