DynamoDB: Apply rough type evaluation and dispatching

[amotl]

When computing values for UPDATE statements, consider the data type of the value. It aims to improve crate/cratedb-toolkit#19 by @hammerhead.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (23452c6) to head (23a2618).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       crate/cratedb-toolkit#24   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          824       828    +4     
=========================================
+ Hits           824       828    +4     

Flag	Coverage Δ
mongodb	100.00% <100.00%> (ø)
vanilla	100.00% <100.00%> (ø)
zyp	100.00% <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.

[hlcianfagna]

We need a test case for the situation of a first level field being an array of objects, for instance

"testarrayobj": [{"field1":1},{"field2":"abc"}]

This cast is successful in CrateDB:

'[{"field1":1},{"field2":"abc"}]'::ARRAY(OBJECT)

[hlcianfagna]

Another situation is the one of a DynamoDB String Set for which CrateDB may have already got an ARRAY(TEXT) defined, but the actual payload may have a single string, for the INSERT or UPDATE to succed we need to wrap this in [ ]

[amotl]

Thank you very much. I am adding your reports to https://github.com/crate/cratedb-toolkit/issues/233#issuecomment-2298485376, in order to merge this patch.