feat(query): Enhance JSON Parsing with Decimal Support and Extended Syntax

[b41sh]

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

Summary

This PR introduces significant enhancements to Databend's parse_json function, focusing on improved numerical precision and expanded syntax support for greater flexibility in handling diverse JSON formats.

Key Changes:

1. Decimal Support for Numbers:

   • Addresses the previous limitation where large numbers in JSON (e.g., 99999999999999999999) would be parsed as floating-point numbers (e.g., 1e20), resulting in a loss of precision.
   • parse_json now supports parsing numbers as Decimal data types, preserving the original precision of large integers.
   • Supports up to 78 digits of precision. Numbers exceeding this limit will still be converted to floating-point representation.

2. Extended JSON Syntax Support:

   • Improves compatibility with a wider range of JSON formats by relaxing certain parsing restrictions.

   • The following extended syntax features are now supported:

     • Empty Array Elements: Arrays can now contain empty elements (e.g., [1,2,,4]), which will be parsed as null values (e.g., [1,2,null,4]).
     • Positive Number Prefix: Numbers are now allowed to have a + prefix (e.g., +123), which will be parsed as the corresponding positive number (e.g., 123).
     • Multiple Leading Zeros: Numbers can now have multiple leading zeros (e.g., 00001), which will be parsed as the equivalent integer (e.g., 1).
     • Missing Digits Around Decimal Point: Numbers can now have missing digits before or after the decimal point (e.g., .1 will be parsed as 0.1, and 1. will be parsed as 1).

Benefits:

• Increased Data Accuracy: Preserves the precision of large numbers when parsing JSON data.
• Improved Compatibility: Handles a wider variety of JSON formats, reducing parsing errors and simplifying data ingestion.
• Enhanced User Experience: Provides a more flexible and forgiving JSON parsing experience.

• fixes: #[Link the issue here]

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