Fix CDS extractor for cds-indexer private package dependency installation (#359)

* Fix CDS extractor cds-indexer deps

Attempt to fix the CDS extractor's support for
private "cds-indexer" package installation by
ensuring that the associated project's entire
node_modules directory is copied instead of just
the cachable subset of the CAP projects NodeJS
dependencies.

* CDS extractor fix dist & test

* fix: CDS extractor support for Windows OS (#360)

* CDS extractor windows fixes - 1

* Fix Windows ENOENT: add shell:true to npm/npx spawn calls

On Windows, npm and npx are .cmd files. execFileSync('npm', ...)
and spawnSync('npx', ...) fail with ENOENT because they bypass the
shell and cannot resolve .cmd extensions. Adding shell: true fixes
this on Windows while being a no-op on Linux/macOS.

Affected files:
- cacheInstaller.ts: execFileSync('npm', ['install', ...])
- projectInstaller.ts: execFileSync('npm', ['install', ...])
- indexer.ts: spawnSync('npx', ['--yes', ...])

* Fix Windows: shell:true for npx spawn, posix paths in LGTM_INDEX_FILTERS

- compile.ts: change shell:false to shell:true so npx (a .cmd on
  Windows) can be resolved during CDS compilation
- environment.ts: use explicit forward-slash paths ('exclude:**/*.*')
  instead of join() which produces backslashes on Windows, causing
  'Illegal use of **' errors in the JS extractor

* Address review feedback for PR #359 (#361)

Author: data-douser

extractors/cds/tools/cds-extractor.ts

@@ -115,6 +115,7 @@ try {
         new Set([
           ...globSync(join(sourceRoot, '**/*.cds'), {
             ignore: ['**/node_modules/**', '**/.git/**'],
+            windowsPathsNoEscape: true,
           }),
         ]),
       );