feat: Version-based token hashes

[pan-kot]

Introducing an alternative way of computing design token hashes. This takes an explicit version, declared per token instead of token's value - allowing the hash to persist even if the value changes, thus giving us granular control over such changes. The idea is to make token hashes stable across a wide range of component versions to make theming simpler.

This is a part of theming improvements project, see QUIP [XEEHAl8Q4kbb].

Once merged, it will be adopted in the components repository. Eventually, all tokens will be migrated over to use a single shared version, but in order to minimise risks - we will migrate tokens in batches. See the first one: cloudscape-design/components#4718

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.22%. Comparing base (9e1e5d4) to head (d2065ea).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #190   +/-   ##
=======================================
  Coverage   97.22%   97.22%           
=======================================
  Files          55       55           
  Lines        1440     1443    +3     
  Branches      264      265    +1     
=======================================
+ Hits         1400     1403    +3     
  Misses         34       34           
  Partials        6        6           

☔ View full report in Codecov by Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[amanabiy]

LGTM!