fix(storage): analyze table get out of index

[zhyass]

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

Summary

This pull request fixes a bug in the “ANALYZE TABLE” logic where the code could attempt to access a block entry by an offset that is out of range (index out of bounds) because the block reader uses a projected column list, but the code uses an original field index. The fix ensures that the correct offset is used when retrieving block entries and prevents the out-of-bounds panic.

• fixes: bug: analyze table get panic #18879

Tests

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

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 

[github-actions]

🤖 CI Job Analysis

Workflow: 18687642258

📊 Summary

• Total Jobs: 83
• Failed Jobs: 2
• Retryable: 0
• Code Issues: 2

❌ NO RETRY NEEDED

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

🔍 Job Details

• ❌ linux / sqllogic / standalone (base, 2c8g, hybrid): Not retryable (Code/Test)
• ❌ linux / sqllogic / cluster (base, 2c8g, 2, hybrid): Not retryable (Code/Test)

---

🤖 About

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