feat: disable error logging stacktrace in message

[CorieW]

Resolves #1681

[Copilot]

Pull Request Overview

Adds a new global option to disable automatic inclusion of error stacktraces in logs and updates the logger and tests to respect this setting.

• Introduce disableErrorLoggingTraceback in GlobalOptions
• Modify entryFromArgs to skip stacktrace when the option is enabled
• Add tests for default stacktrace inclusion and disabling behavior

Reviewed Changes

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

File	Description
src/v2/options.ts	Add disableErrorLoggingTraceback to GlobalOptions with accompanying JSDoc
src/logger/index.ts	Check getGlobalOptions().disableErrorLoggingTraceback before injecting stacktrace
spec/logger.spec.ts	Tests for error logging behavior with and without the new option

Comments suppressed due to low confidence (2)

src/v2/options.ts:241

• Fix the JSDoc wording to remove the double negative, e.g. When true, the error message will not include the traceback of the error.

* When true, the error message will include not include the traceback of the error.

spec/logger.spec.ts:223

• Consider adding a test case where logger.error is called with an actual Error object to ensure that existing Error instances aren’t wrapped with a new stacktrace.

describe("error logging stacktrace", () => {

[Copilot]

After modifying global options in tests, reset or restore them (e.g., in an afterEach) to avoid state leakage between tests.

Suggested change

	const message = "Test error with traceback disabled";
	const message = "Test error with traceback disabled";
	const originalOptions = { ...setGlobalOptions() }; // Save original global options