feat: add triggerReason to pet.process_restart and globalScopeDeferred to setup.hang_detected

[eleanorjboyd]

• pet.process_restart now emits triggerReason (process_exit::, process_error, rpc_connection_error, rpc_refresh_timeout, rpc_resolve_timeout, rpc_configure_timeout, start_failed, unknown) so we can distinguish crash restarts from timeout restarts.
• setup.hang_detected now emits globalScopeDeferred (true/false/undefined) so we can tell whether a watchdog trip was a real foreground hang or a background global-scope scan running past 120s after the user already had an env selected

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

This PR enhances telemetry around PET restarts and activation hang detection to better attribute why PET restarted and whether setup hangs are related to deferred global-scope environment resolution.

Changes:

• Add triggerReason to pet.process_restart telemetry to distinguish restarts caused by exit vs RPC timeouts/errors.
• Track whether global-scope resolution was deferred during initial environment selection and include it in setup.hang_detected telemetry.
• Extend telemetry schema (constants.ts) to include the new properties in GDPR mappings and typings.

Show a summary per file

File	Description
src/managers/common/nativePythonFinder.ts	Tracks PET exit/restart reasons and includes triggerReason in restart telemetry.
src/features/interpreterSelection.ts	Adds a mutable ref to record whether global-scope resolution was deferred vs awaited.
src/extension.ts	Plumbs globalScopeDeferred into hang watchdog telemetry via a shared ref.
src/common/telemetry/constants.ts	Updates telemetry schema/GDPR mapping for globalScopeDeferred and triggerReason.

Copilot's findings

Comments suppressed due to low confidence (1)

src/managers/common/nativePythonFinder.ts:545

• The error handler sets processExitReason = 'process_error' unconditionally; if a more-specific reason was already recorded (e.g., an RPC timeout/connection error followed by a kill), this will overwrite it and reduce the fidelity of triggerReason telemetry. Consider only setting this when processExitReason is still undefined.

            // Handle process errors (e.g., ENOENT if executable not found)
            this.proc.on('error', (err) => {
                this.processExited = true;
                this.processExitReason = 'process_error';
                this.outputChannel.error('[pet] Process error:', err);

• Files reviewed: 4/4 changed files
• Comments generated: 5

[Copilot]

Copilot's findings

• Files reviewed: 4/4 changed files
• Comments generated: 3