refactor: (WIP)exprimental parquet reader

[dantengsky]

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

Summary

This PR introduces an experimental Parquet deserialization component aimed at improving the efficiency of Parquet data deserialization for Fuse tables.

This PR is the first part of a series of improvements.

However, many additional features and capabilities still need to be implemented (TODO: add details todo items).

Initial testing on TPC-H SF 1000 shows that the optimizations are effective:

Comparison of scanning columns of table lineitem

• using select col from lineitem ignore_result
• data fully cached on local nvme ssd
• warm up before each measure (columns almost all in page cache for each measured run)

Column Type	experimental_reader (s)	production_reader (s)	experimental: production
l_orderkey (BIGINT)	4.479	5.719	78.32%
l_partkey (BIGINT)	5.424	7.17	75.65%
l_suppkey (BIGINT)	4.855	6.738	72.05%
l_linenumber (BIGINT)	4.264	4.824	88.39%
l_quantity (DECIMAL)	4.16	16.563	25.12%
l_extendedprice (DECIMAL)	4.74	18.316	25.88%
l_discount (DECIMAL)	4.598	15.849	29.01%
l_tax (DECIMAL)	4.514	15.813	28.55%
l_returnflag (VARCHAR)	4.641	11.36	40.85%
l_linestatus (VARCHAR)	4.495	11.833	37.99%
l_shipdate (DATE)	0.446	1.392	32.04%
l_commitdate (DATE)	2.24	2.758	81.22%
l_receiptdate (DATE)	2.17	2.561	84.73%
l_shipinstruct (VARCHAR)	9.01	17.387	51.82%
l_shipmode (VARCHAR)	6.059	13.922	43.52%
l_comment (VARCHAR)	20.381	38.873	52.43%

To enable to experiment reader set use_parquet2 = 1 (will be changed to other setting later)

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]

🤖 Smart Auto-retry Analysis

Workflow: 16871687290

📊 Summary

• Total Jobs: 22
• Failed Jobs: 1
• Retryable: 0
• Code Issues: 1

❌ NO RETRY NEEDED

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

🔍 Job Details

• ❌ linux / check: Not retryable (Code/Test)

---

🤖 About

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