Add debug task

[lszomoru]

No description provided.

[Copilot]

Pull request overview

This PR adds a debug task to the macOS Darwin test workflow to output the result of the computeNodeModulesCacheKey.ts script to the console for debugging purposes. This runs immediately before the existing "Prepare node_modules cache key" step, which saves the same output to a file.

Key Changes

• Added a new debug step that executes computeNodeModulesCacheKey.ts without redirecting output to a file, allowing the cache key to be visible in workflow logs

[Copilot]

This debug task runs the same script twice in succession, which adds time to the CI pipeline. If this is temporary debugging code, consider removing it before merging. If permanent, consider adding a comment explaining why the debug output is needed or consolidating it with the actual cache key preparation step using tee to both display and save the output: node build/azure-pipelines/common/computeNodeModulesCacheKey.ts darwin $VSCODE_ARCH $(node -p process.arch) | tee .build/packagelockhash.

Suggested change

	- name: Prepare node_modules cache key (debug)
	run: node build/azure-pipelines/common/computeNodeModulesCacheKey.ts darwin $VSCODE_ARCH $(node -p process.arch)
	- name: Prepare node_modules cache key
	run: mkdir -p .build && node build/azure-pipelines/common/computeNodeModulesCacheKey.ts darwin $VSCODE_ARCH $(node -p process.arch) > .build/packagelockhash
	- name: Prepare node_modules cache key
	run: mkdir -p .build && node build/azure-pipelines/common/computeNodeModulesCacheKey.ts darwin $VSCODE_ARCH $(node -p process.arch) | tee .build/packagelockhash