Refactor named imports to default instead of namespace when esModuleInterop is on and module is an export=

[andrewbranch]

If a module declares an export =, we let you import the resolved export’s members with named imports, but this is generally asking for a bad time. If you have esModuleInterop enabled, the best thing to do with an export = is to default-import it. However, the refactor we offer is to convert the named imports to a namespace (import *) import. That’s definitely the most correct translation from named imports, but if you were already doing something super sketchy by using named imports, we can nudge you in the direction of doing something better by replacing them with a default import instead a namespace import.

Closes #46047

[sandersn]

If a module declares an export =, we let you import the resolved export’s members with named imports, but this is generally asking for a bad time

I have only ever had a good time doing this.

[andrewbranch]

That's because you like to avoid classes