fix(ci): rm workspace node_modules

[reggi]

Fixes #7226, an issue where the npm ci needs to remove node_modules within workspace directories.

[npm-cli-bot]

no statistically significant performance changes detected

timing results

app-large	clean	lock-only	cache-only	modules-only	no-lock	no-cache	no-modules	no-clean	show-version	run-script	cache-only peer-deps	no-clean audit
npm@latest	31.277 ±0.66	10.773 ±0.03	11.725 ±0.07	1.533 ±0.02	1.543 ±0.00	1.271 ±0.01	8.303 ±0.01	1.261 ±0.01	0.137 ±0.00	0.169 ±0.01	14.928 ±0.17	2.096 ±0.00
#7490	33.998 ±2.64	10.665 ±0.03	12.338 ±0.37	1.604 ±0.05	1.549 ±0.01	1.294 ±0.01	8.403 ±0.01	1.276 ±0.01	0.137 ±0.00	0.164 ±0.00	14.636 ±0.20	2.116 ±0.04

app-medium	clean	lock-only	cache-only	modules-only	no-lock	no-cache	no-modules	no-clean	show-version	run-script	cache-only peer-deps	no-clean audit
npm@latest	24.931 ±0.50	8.021 ±0.01	8.891 ±0.04	1.493 ±0.01	1.490 ±0.01	1.395 ±0.01	5.771 ±0.05	1.295 ±0.01	0.137 ±0.00	0.164 ±0.00	9.952 ±0.02	1.993 ±0.08
#7490	25.700 ±2.44	8.172 ±0.13	8.972 ±0.06	1.524 ±0.00	1.540 ±0.03	1.403 ±0.01	5.843 ±0.02	1.291 ±0.01	0.138 ±0.00	0.164 ±0.00	9.932 ±0.05	2.053 ±0.10

[lukekarrys]

CI extends ArboristWorkspaceCmd which will call this.setWorkspaces() and then this.exec(). So we can check if this.workspacePaths is set and use that instead of calling getWorkspaces directly. Also ArboristWorkspaceCmd will always set includeWorkspaceRoot: false so we need to explicitly include where.

We need to do this because you can run npm ci -w workspace-a and have it only install the deps for workspace-a but you can't guarantee that the root node_modules won't end up populated. So in fixing this bug we want to make sure that we only rm -rf the node_modules specified by the workspace config, plus the root.