fix(cubesql): Match CubeScan timestamp literal types to member types

[MazterQyou]

Check List

• Tests have been run in packages where changes made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

Description of Changes Made

This PR changes type of timestamp literal values in CubeScan to TimestampNanosecond. They previously converted to TimestampMillisecond which does not match member type (which is actually TimestampNanosecond despite Cube returning millisecond precision values). This led to issues with two CubeScans, one containing a member and another a literal, being unable to UNION.

Example plan that fails to execute:

Union
  Projection: CAST(NULL AS Timestamp(Millisecond, None)) AS date, #SUM(amount) AS amount
    Aggregate: groupBy=[[]], aggr=[[SUM(#cube.amount)]]
      TableScan: cube projection=None
  Projection: #cube.date AS date, #SUM(amount) AS amount
    Aggregate: groupBy=[[#cube.date]], aggr=[[SUM(#cube.amount)]]
      TableScan: cube projection=None

As Cube date time columns are considered TimestampMillisecond, initial planning provides Millisecond type; but CubeScan member types are TimestampNanosecond, and two CubeScans cannot be unioned in this case. As such, rewriting produces an invalid plan.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.65%. Comparing base (1dfa10d) to head (d229fcf).
Report is 6 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #9275   +/-   ##
=======================================
  Coverage   83.65%   83.65%           
=======================================
  Files         227      227           
  Lines       81773    81773           
=======================================
  Hits        68409    68409           
  Misses      13364    13364           

Flag	Coverage Δ
cubesql	83.65% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.