Issue Description:

If I call String(describing: ) on an instance of trivial struct type, it prints a call to the constructor. Ex.,

struct ExampleSwiftStruct {
    let exampleMember: Float
}

print("\(String(describing: ExampleSwiftStruct(exampleMember: 2)))") //ExampleSwiftStruct(exampleMember: 2.0)

(I think this behavior is technically unspecified, but it's a very useful behavior for printing problematic values and then pasting them into playgrounds or unit tests.)

However in the case that the type was refined for Swift, the behavior is a bit odd

__attribute__((swift_name("ExampleCStruct")))
typedef struct {
    __attribute__((swift_name("exampleMember")))
    float unrefinedCMember;
    
} UnrefinedCType;

prints

UnrefinedCType(exampleMember: 2.0)

e.g. with the unrefined name as the type being constructed, but the refined name of the member.

Ideally, Swift would use the refined name in both places. It's possible to provide custom implementations of the appropriate protocols and then get defined behavior, but for debugging the large universe of C types it's not an ideal situation.