fix: sync fs esm library after patching cjs version

[jbedard]

For example as a test... without the syncBuiltinESMExports the last log (5) is false:

    import('fs').then(importFS => {
        console.log(1, origReaddirSync === fs.readdirSync)          // pre patched
        console.log(2, origReaddirSync === importFS.readdirSync)    // pre patch
        patchfs(fs, roots)
        console.log(3, origReaddirSync !== fs.readdirSync)          // post patched
        console.log(4, origReaddirSync === importFS.readdirSync)    // pre synced
        module.syncBuiltinESMExports()
        console.log(5, origReaddirSync !== importFS.readdirSync)    // post sync
    });

[matthewjh]

@jbedard, will this address #362?

[jbedard]

No it does not.

In #362 the fs methods are destructed using cjs: {...} = require('fs'). This PR addresses the case where the fs methods are destructed using esm: import {...} from 'fs', and we haven't actually observed this esm case anywhere so I'm not sure if this will actually land.

[matthewjh]

I see. Well, it seems useful to me, just in case someone in 1p code or a library decides to do this.

What are the downsides to merging?

[jbedard]

Just the possibility of breaking something. I'd prefer merging and giving it a shot though...

[gregmagolan]

🌮