Tracking: issues about new expression

[sundy-li]

Summary

After we merge #9411, it may have some issues to solve before we release the next version of 0.9.

• Delete functions, datablocks crate and rename functions-v2. chore(query): remove and rename crates #9481
• Support alter table refresh index to override the indices in new version, instead we have be compatible index in chore(expression): be compatible with version v2 bloom filter index #9511
• chore(fuse): make column meta to be an enum #9562
• Improve bloom filter to use vectorized & typed hash function rather than hashing the ScalarRef enum refactor(storage): refactor bloom index to use vectorized siphash function #9542
• read_parquet support read nested datatype. feat(storage): support nested type in read_parquet. #9486
• functions support set error which respect an option null mask bitmap during the evaluation refactor(query): use ctx to store the function evaluation error #9501
• performance: hits dataset performance degradation in new expression #9483
• bug: memory allocation of 2284800604532 bytes failed and databend-query hang #9497
• chore(expression): add try adaptor in function #9533

Meta-service:

• feat(meta/proto-conv): add reader-min-msg-ver and msg-min-reader-ver #9535
• chore(meta/proto): rename message.min_compatible to message.min_reader_ver to reflect its actual purpose #9544
• refactor(meta/proto-conv): revert and fix proto-conv test for new Schema types #9555
• feat(meta): use expressin::TableSchema to replace obsolete datavalues::DataSchema #9506
• Meta provides a tool to migrate meta between versions. feat(meta/upgrade): meta data upgrade program #9489
• Save the new schema format TableSchema directly to meta-service, without converting back to obsolete DataSchema. #9498

[drmingdrmer]

Update meta-service related task:
Save the new schema format TableSchema directly to meta-service, without converting back to obsolete DataSchema.

[sundy-li]

Update meta-service related task: Save the new schema format TableSchema directly to meta-service, without converting back to obsolete DataSchema.

That's ok I think, we can backup the obsolete meta.