fix(@jcoreio/toolchain-esnext): fix mocha CJS resolution issues

In a project with `outputEsm: false`, mocha's `importOrRequire` can end up trying to import
the file via `babelRegisterEsmWrapper` ^Cd failing with a "require is not defined in ES"
error that it mocha doesn't identify as a reason to try `require`ing the file instead.

fix(@jcoreio/toolchain-typescript): add moduleDetection: force to def…

…ault config

fix(@jcoreio/toolchain-esnext): don't transpile file with default ext…

… when alt type ext exists (#41)

fix(@jcoreio/toolchain-esnext): fix resolved import extension replace…

…ment

fix: url vs string type error

fix: resolve alternate module types for absolute paths (#40)

fix: obscure crash in mochaWatchClearConsole

fix: remove sourcesContent from output souces maps

fix #39

feat: automatically resolve to .cjs/.cts files in test:cjs, fix modul…

…e resolution issues in test:esm (#38)

Merge pull request #37 from jcoreio/type-module

feat: output .cjs/.js when package has type: module