Fix panic handling in DoCommit to prevent blocking on database driver panics

[Copilot]

When underlying database drivers panic during SQL operations, the DoCommit function would propagate the panic unhandled, causing Insert operations to block indefinitely instead of returning proper errors. This was particularly problematic with ClickHouse when using *big.Int values that exceed column type limits (e.g., int128).

Problem

The issue manifested in the following scenario:

1. User inserts data with *big.Int value larger than ClickHouse int128 capacity
2. ClickHouse driver panics with "math/big: buffer too small to fit value"
3. Panic propagates through the call stack: big.nat.bytes → ClickHouse driver → gdb.(*Core).DoCommit
4. Insert operation blocks indefinitely, returning neither success nor error

Solution

Added comprehensive panic recovery to the DoCommit function in database/gdb/gdb_core_underlying.go:

// Panic recovery to handle panics from underlying database drivers
defer func() {
    if exception := recover(); exception != nil {
        if err == nil {
            if v, ok := exception.(error); ok && gerror.HasStack(v) {
                err = v
            } else {
                err = gerror.WrapCodef(gcode.CodeDbOperationError, 
                    gerror.NewCodef(gcode.CodeInternalPanic, "%+v", exception), 
                    FormatSqlWithArgs(in.Sql, in.Args))
            }
        }
    }
}()

Benefits

• Prevents blocking: Insert operations now return errors instead of hanging
• Proper error context: Errors include full SQL statement and arguments for debugging
• Graceful degradation: Applications can handle driver panics appropriately
• Backward compatibility: No breaking changes to existing functionality
• Universal coverage: Protects against panics from any database driver

Testing

Added comprehensive tests covering:

• String panic values (e.g., "math/big: buffer too small")
• Error panic values with stack traces
• Various SQL operation types (Insert, Query, Prepare, etc.)
• Error message formatting and context preservation

All existing tests continue to pass, ensuring no regressions.

Fixes #4372.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.