feat: redact username in logging paths

[yCodeTech]

This pull request introduces a new warning log level and improves logging safety by redacting OS usernames in paths from log output. It also refines the handling of extension discovery paths and updates log level descriptions for clarity.

Logging improvements:

• Added a new warn log level, including support in the logger, log level comparisons, and the logLevels utils constant.
• Implemented automatic redaction of the current OS username from all log messages and data to prevent accidental leaking of sensitive information. If the username cannot be determined, a warning is logged once per session while avoiding infinite recursion, and further redaction attempts are skipped.

Configuration and API updates:

• Updated log level descriptions in package.json to reflect the new warn level and clarify which messages are included at each level.
• The getAllExtensionDiscoveryPaths method now returns a new Map to prevent external mutation of internal state.

Other changes:

• Minor code formatting and comments for clarity in configuration and extension data classes.

[Copilot]

Pull request overview

This PR adds a reusable redaction utility to prevent leaking the current OS username in log output, and applies it to a few high-signal logging/data-access paths in the extension.

Changes:

• Added redactUsername in src/utils.ts to recursively redact usernames in strings across nested data structures.
• Updated Configuration.logDebugInfo() logging to redact usernames from environment data and language config file paths.
• Updated ExtensionData to redact usernames in extensionPath and extension discovery paths when used for logging.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/utils.ts	Introduces redactUsername utility used for recursive username redaction in log-bound data.
src/configuration.ts	Applies username redaction to debug logging of environment/config path-related data.
src/extensionData.ts	Redacts username from extension path and discovery paths exposed for logging.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (3)

src/logger.ts:233

• Username redaction is currently only applied to the formatted meta output (via formatMeta()), not to the main message string appended in logMessage(). This still allows usernames to leak when call sites interpolate paths directly into the message (e.g., logger.info(Loaded DEV_USER_EXTENSIONS_PATH: "${devPath}") in src/utils.ts). Consider redacting the message before appending it to the output channel (and ideally also for important() logs) so redaction is consistently applied.

			data = lines.join(",\n");
		}

		return this.redactUsername(data);
	}

src/logger.ts:299

• The warning text says "debug logs may not be redacted", but username redaction is applied to any log meta that goes through formatMeta() (including info/warn/error). The message should be accurate so users understand the scope of the redaction failure.

		this.warn("Could not determine OS username; debug logs may not be redacted before sharing.");

src/logger.ts:261

• PR description says a recursive redactUsername utility was added to src/utils.ts and applied across configuration/extension data accessors, but the implementation shown here adds redaction inside Logger instead. Please update the PR description (or align the implementation) so it accurately reflects where redaction lives and how it’s applied.

	/**
	 * Redact the OS username from a string, replacing it with `<redacted>`, to avoid leaking
	 * it into debug logs that could be shared.
	 *
	 * @param {string} text The text to redact.