feat: use parquet-rs as an alternative in fuse engine

[SkyFan2002]

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

Summary

Migrate scope

Migrated to parquet-rs in this PR:

1. Fuse table block(read, write)
2. Aggregation index(read, write)
3. copy into stage(write)

Still parquet2: （They read parquet in different code paths, so I decide to split into different PRs

1. Result cache(read,write)
2. virtual column(read,write)
3. stream load(read parquet)
4. bloom index(read, write)

Compatibility

Backwards compatibility is tested by

statement ok
SET fuse_write_use_parquet2 = 1;

statement ok
SET fuse_read_use_parquet2 = 0;

in sql logic test.

Fixes #14135

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 

[JackTan25]

can we get parquet write performance improvement after using parquet-rs in this pr? @SkyFan2002

[SkyFan2002]

can we get parquet write performance improvement after using parquet-rs in this pr? @SkyFan2002

No. Do you have any concerns?

[JackTan25]

can we get parquet write performance improvement after using parquet-rs in this pr? @SkyFan2002

No. Do you have any concerns?

At least hopefully there is no performance reducing.

[github-actions]

Docker Image for PR

• tag: pr-14268-cf683bb

note: this image tag is only available for internal use,
please check the internal doc for more details.

[github-actions]

ClickBench Report

• hits: https://benchmark.databend.rs/clickbench/pr/14268/7696024130/hits.html
• tpch: https://benchmark.databend.rs/clickbench/pr/14268/7696024130/tpch.html