fix(sql): support unsigned ASOF join keys

[sundy-li]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

• extend ASOF join boundary generation to support unsigned integer join keys
• replace ASOF boundary unwrap() calls with BadDataValueType propagation so unsupported types return an error instead of panicking
• add an expression-level regression test plus an unsigned ASOF sqllogictest case

Fixes #19570

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Validation:

• cargo test -p databend-common-expression --test it test_integer_infinity_boundaries
• cargo clippy -p databend-common-sql --lib --tests -- -D warnings

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b940b91509

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[sundy-li]

Found a blocking issue in the unsigned ASOF sentinel handling. Using the type-domain max/min as infinity() / ninfinity() makes the rewrite drop valid boundary matches (>= at MAX and <= at MIN). See the inline comment for a concrete example.

[sundy-li]

Focused verification passed, but the new unsigned sentinels still make ASOF results wrong at the legal type boundaries. rewrite_asof() uses infinity()/ninfinity() as the LEAD default and then applies strict < / > bounds, so rows at UInt*_MAX or UInt*_MIN cannot match the terminal or initial interval even though they should. This means unsigned ASOF joins are still incorrect for valid key values and need a different unbounded strategy or dedicated operator before this lands.

[github-actions]

🤖 CI Job Analysis

Workflow: 23517289205

📊 Summary

• Total Jobs: 86
• Failed Jobs: 4
• Retryable: 0
• Code Issues: 4

❌ NO RETRY NEEDED

All failures appear to be code/test issues requiring manual fixes.

🔍 Job Details

• ❌ linux / sqllogic / cluster (duckdb, 4c, hybrid): Not retryable (Code/Test)
• ❌ linux / sqllogic / cluster (duckdb, 4c, http): Not retryable (Code/Test)
• ❌ linux / sqllogic / standalone (duckdb, 4c, http): Not retryable (Code/Test)
• ❌ linux / sqllogic / standalone (duckdb, 4c, hybrid): Not retryable (Code/Test)

---

🤖 About

Automated analysis using job annotations to distinguish infrastructure issues (auto-retried) from code/test issues (manual fixes needed).