Implement PropagateSkip and NewErrorSkip for Custom Frame Skipping - #1

This pull request introduces new functions to the stacktrace package: PropagateSkip, NewErrorSkip, and their variants. These functions allow users to skip an arbitrary number of frames in the stack trace, thereby enabling better stack trace reporting in helper functions. This solves the issue where the original invocation point of a helper function was replaced by the helper itself in the stack trace.

• New Functions Introduced:

  • NewErrorSkip(skip int, msg string, vals ...interface{}) error: Creates a new error with the ability to skip specified stack frames.
  • PropagateSkip(cause error, skip int, msg string, vals ...interface{}) error: Propagates an error while allowing skip of frames.
  • NewErrorWithCodeSkip(code ErrorCode, skip int, msg string, vals ...interface{}) error: Similar to NewErrorWithCode, but allows skipping frames.
  • ErrorBuilder: Enhanced class to construct errors with custom skip values.

• Testing: New tests in skip_test.go confirm that the correct caller information is maintained and that the helper function itself does not appear in the error string when using PropagateSkip and the builder methods.

These changes enhance usability for error handling within our libraries.

This pull request was co-created with Cosine Genie

Original Task: stacktrace/866fqf1v1hka
Author: Pandelis Zembashis