Variable Length Decimal Support to Handle Cube Store Parquet Data Type Issues

**Describe the bug**
When leveraging a MySQL decimal field that is defined as DECIMAL(65,30), the pre-aggregated results cannot be stored within Cube Store.

**To Reproduce**
Steps to reproduce the behavior:
1. Create a MySQL table (likely any database will do as its a Parquet conversion issue) with DECIMAL(65,30).
2. Insert extremely large values in this field.
3. Perform an aggregate query using SUM
4. Define as a pre-aggregate query
5. Watch the CREATE TABLE process fail when using Cube Store as your pre-aggregate data store repository.

**Expected behavior**
1. Ideal behavior - Cube Store can correctly map data types of this nature.
2. Acceptable behavior - Variable length can be defined as part of your measurement definition for pre-aggregate consumption

**Screenshots**
N/A

**Version:**
Current

**Additional context**
None