enhancement/issue 1439 handle excessive lifecycle running due to Worker thread spawning triggering the register function

[thescientist13]

Related Issue

resolves #1439

Documentation

N / A

Summary of Changes

1. Only invoke register.js when using --import when it actually comes from Greenwood

Demo / repro repo - https://github.com/thescientist13/greenwood-lifecycles-demo

TODO

1. Windows tests failing - maybe due to needing to use path.sep?

Question

1. read / write configuration to disk? - configuration lifecycle is running excessively (related to custom loaders usage?) #1439 (comment)
2. need to cover more cases?

   // @@@@ REGISTER [
   //   '/Users/owenbuckley/.local/share/mise/installs/node/22.14.0/bin/node',
   //   '/Users/owenbuckley/Workspace/github-forks/HP_Stuff/packages/greenwood/node_modules/@greenwood/cli/src/index.js',
   //   'develop'
   // ]
   
   // @@@@ REGISTER [
   //   '/Users/owenbuckley/.local/share/mise/installs/node/22.14.0/bin/node',
   //   '/Users/owenbuckley/Workspace/github-forks/HP_Stuff/node_modules/.pnpm/@[email protected]/node_modules/@greenwood/cli/src/lib/ssr-route-worker.js'
   // ]
   if(process.argv.filter(arg => arg.endsWith('.bin/greenwood') || arg.indexOf('@greenwood/cli/src') >= 0).length === 1) {
     register("./loader.js", import.meta.url);
   }

3. Confirm if this is expected behavior / outreach (I think it is)
4. Is there a better way then checking process.argv