This PR addresses the discussion in #9339 by enhancing error reporting with C++ and Status propagation stack traces. The main goal is to provide more informative error messages by including both C++ stacktraces and Status propagation stacktraces. This should help developers quickly pinpoint error origins and understand how errors propagate through the system, simplifying debugging.

Key Changes:

• Moved MaybeWithLocation and MaybeWithNewMessage to the status_internal namespace, as they are intended for internal use only.
• Implemented the use of Status payload for separate storage of the status propagation stacktrace.
• Added functionality to dump the C++ stacktrace by calling tsl::CurrentStackTrace() immediately before throwing an exception.
• Adapted existing tests in test_status_common.h to reflect these changes.
• Introduced a new test, MaybeThrowWithErrorPropagationWithNewMessage, to demonstrate the format of the enhanced error messages.
• Renamed testing global variables in test_status_common.h to adhere to the kVarName pattern.

Update: added the function name __FUNCTION__ to the status propagation trace. Lambda functions are recorded as operator().

Before:

• No C++ stacktrace
• Line 342, which propagates the status, is not mentioned

RuntimeError: New test error message (at ./test/cpp/test_status_common.h:335)
    From Error: Test error message (at ./test/cpp/test_status_common.h:329)

After:

RuntimeError: New test error message

Status Propagation Stacktrace:
    From: foo at ./test/cpp/test_status_common.h:329 (error: Test error message)
    From: bar at ./test/cpp/test_status_common.h:335 (error: New test error message)
    From: baz at ./test/cpp/test_status_common.h:342

C++ Stacktrace:
*** Begin stack trace ***
        ...
        __libc_start_main
*** End stack trace ***