related: #950

so some versions of node (19 - 20 ) in the transition from --loaders to --imports broke the execution order of loaders, in a way the spec around loaders using other loaders was kinda janky.

looking at https://github.com/tapjs/tapjs/blob/main/src/run/src/test-argv.ts#L44-L51 and pulling out combinations of what's generated for 20.5 we see

node \
--loader=./node_modules/@isaacs/ts-node-temp-fork-for-pr-2009/esm.mjs \
--loader=./node_modules/@tapjs/mock/dist/esm/legacy-loader.mjs \
--enable-source-maps \
--loader=./node_modules/@tapjs/processinfo/dist/esm/loader-legacy.mjs \
./test/main.js

this fails, however when you remove the processinfo loader it passes, or when you remove the mock it works, which led me to think this was an error with chaining the two.

the issue lies in the mock loader reading in the processinfo imports before the mock has be initialized this can be fixed in three ways.

1. just don't throw for the mock loader, the initial calls are all from processinfo then the mock loader initializes and it works again
2. as in this pr, don't throw after the mock loader has initialized the client
3. some kind of janky ban list of modules that processinfo uses like which works but it's really manual

const invalid = (url) => {
    if (!url) return false
    return (
        url.includes('/node_modules/@tapjs/processinfo') ||
        url.includes('/node_modules/uuid/') ||
        url.includes('/node_modules/process-on-spawn/') ||
        url.includes('/node_modules/signal-exit/') ||
        url.includes('/node_modules/pirates/') ||
        url.includes('/node_modules/signal-exit/') ||
        url === 'node:inspector'
    )
}