feat(query): pre-check cast type

[andylokandy]

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

Summary

Tests

• [x] Unit Test
• [ ] Logic Test
• [ ] Benchmark Test
• [ ] No Test - Explain why

Type of change

• [ ] Bug Fix (non-breaking change which fixes an issue)
• [x] 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 

[what-the-diff[bot]]

PR Summary

• Improved Data Type Conversion Functionality We have improved the 'check_cast' function, which is used to convert or translate data from one type to another. This enhancement now allows for more diverse and extra conversion rules among various data types.

• Incorporated Detailed Scenario Handling A comprehensive set of rules (referred to as a match statement) has been designed and implemented to deal with specialized conversion scenarios. This includes the different cases such as 'Null', 'Nullable', 'Array', and 'Map' data types.

• Enhanced Conversion between 'Variant' and 'Map', and between 'Tuple' types The functionality to convert from 'Variant' to 'Map' (with tuple type) and from one 'Tuple' to another 'Tuple' has been added. The only condition for this conversion is that the source and destination tuples should have an equal number of data type components.

• Robust Error Handling In the event of a situation where data conversion is not feasible or supported, our improved error handling mechanisms will produce a detailed, meaningful error message. This feature helps in understanding what went wrong and aids in troubleshooting.

[sundy-li]

please check the ci