fix(nano): use Uint32 for Timestamp instead of Int32

[jansegre]

Motivation

Timestamps don't make use of negative integers, so it's not useful to use a signed integer encoding.

Acceptance Criteria

• Introduce Uint32NCType that is similar to Int32NCType but unsigned instead of signed
• Change Timestamp's mapping to Uint32NCType

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged

[github-actions]

Bencher Report

Branch	fix/use-uint32-for-timestamp
Testbed	ubuntu-22.04

Click to view all benchmark results

Benchmark	Latency	Benchmark Result minutes (m) (Result Δ%)	Lower Boundary minutes (m) (Limit %)	Upper Boundary minutes (m) (Limit %)
sync-v2 (up to 20000 blocks)	📈 view plot 🚷 view threshold	1.65 m (+0.98%) Baseline: 1.64 m	1.47 m (89.12%)	1.80 m (91.80%)

🐰 View full continuous benchmarking report in Bencher

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.60%. Comparing base (4daccef) to head (c2e6138).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1316      +/-   ##
==========================================
+ Coverage   85.59%   85.60%   +0.01%     
==========================================
  Files         424      424              
  Lines       31986    31989       +3     
  Branches     4967     4967              
==========================================
+ Hits        27377    27385       +8     
+ Misses       3607     3606       -1     
+ Partials     1002      998       -4     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.