Incorrect CJS import with `esmoduleInterop: true`

Repro: https://github.com/BeeeQueue/esbuild-cjs-no-default

TL;DR: `import core from "@actions/core"` generates invalid code which fails when running, presumably because it does something funky with the exports somewhere.

I tried to look around a bit to see if I could find what they're doing weird but couldn't find anything myself.

It can be worked around with `import * as`, but if that is the intended behavior there should probably be a warning about it.

Maybe related to #1079?

Start with the linked reproduction at https://github.com/BeeeQueue/esbuild-cjs-no-default and inspect the generated code for `import core from "@actions/core"` with `esModuleInterop: true`. Compare its runtime behavior with the `import * as` workaround and determine whether the expected outcome is valid execution or a warning for this import pattern.

Written by the indexing model from the issue text.