Fix derby/server cluster imports

[craigbeck]

Downstream code failing when using derby/server as cluster imported in trasformed with default import like this:

// there is no cluster.default
 if (cluster.default.isPrimary) {
    console.log('Primary PID ', process.pid);
    startWorker();
  }

and erors with default is undefined

Additionally added forward compatible mapping for pre node16 module resolutions for server

[ericyhwang]

Seems to be a mismatch in types vs runtime:

• @types/node indicates that the built-in "cluster" module is an ES module
• We compile to CommonJS, so TS inserts the extra .default to allow usage of a (supposed) ES module's default after using a CommonJS require
• However, because the output JS is using require, Node provides the CommonJS version of "cluster", not the ESM version

This could also be resolved by using esModuleInterop in tsconfig, but I'm reluctant to do that because of the extra helper functions inserted in each output file by TS when using that option.