Default imports for some modules behave differently when statically imported on client side vs server side

[lionel-rowe]

Default imports for some modules, such as npm:prettier@3.3.3/parser-html, behave differently when statically imported on the client side vs server side.

Repro:

1. Bootstrap app with deno run -A -r https://fresh.deno.dev

2. Replace content of islands/Counter.tsx with the following:

   import * as staticMod from 'npm:prettier@3.3.3/parser-html'
   import { assert } from "jsr:@std/assert@1.0.6";
   
   const dynamicMod = await import('npm:prettier@3.3.3/parser-html')
   
   assert('default' in dynamicMod, 'No default prop (dynamic)!')
   console.log('ok (dynamic)')
   
   assert('default' in staticMod, 'No default prop! (static)')
   console.log('ok (static)')
   
   export default function() {
     return <div>...</div>
   }

3. Observe output in CLI console:

   ok (dynamic)
   ok (static)
   

4. Open server URL and observe output in browser console:

   ok (dynamic)
   assert.ts:21 Uncaught AssertionError: No default prop! (static)
       at assert (assert.ts:21:11)
       at Counter.tsx:9:1
   

On the server, both staticMod and dynamicMod are module objects with default props; however, on the client, staticMod is itself the default export (i.e. it doesn't have a default prop of its own).