Warn if timestamp updated_at field uses incompatible timestamp

[gshank]

resolves #10234

Problem

Snapshot tables use the 'get_snapshot_time' macro, which may be incompatible with the data type of the field specified as the 'updated_at' field, causing unexpected results.

Solution

Warn if the two sources of timestamp columns have different data types.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
• This PR includes type annotations for new and modified functions

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.74%. Comparing base (ca163c3) to head (871052c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10352      +/-   ##
==========================================
- Coverage   88.75%   88.74%   -0.02%     
==========================================
  Files         180      180              
  Lines       22486    22497      +11     
==========================================
+ Hits        19958    19964       +6     
- Misses       2528     2533       +5     

Flag	Coverage Δ
integration	86.00% <100.00%> (-0.02%)	⬇️
unit	62.19% <87.50%> (-0.01%)	⬇️

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.

[MichelleArk]

nit: are two changelog entries intentional?