fix: use column name instead of field name for redis cache key

[wschurman]

Why

Having the cache key on field name means that field renames need to bump the cache key for the entity itself, which is non-obvious (we've been bit by it twice at Expo). Instead, it makes more sense to cache keyed by column name which is much clearer that a cache key bump is needed when changed.

Closes #107.
Closes ENG-291.

How

Change to use column name in key generation function.

Note that upgrading to a version that includes this change will cause a full entity cache invalidation of all entities. This should be fine for most applications but was why we were hesitant to make this change previously. Now the benefits outweigh the costs though.

Test Plan

Run all tests.

[linear]

ENG-291 cache key on column name instead of field name in entity

[codecov]

Codecov Report

Merging #124 (76a3256) into master (eaab0b1) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #124   +/-   ##
=======================================
  Coverage   95.10%   95.10%           
=======================================
  Files          67       67           
  Lines        1694     1697    +3     
  Branches      203      183   -20     
=======================================
+ Hits         1611     1614    +3     
  Misses         81       81           
  Partials        2        2           

Flag	Coverage Δ
integration	95.10% <100.00%> (+<0.01%)	⬆️
unittest	95.10% <100.00%> (+<0.01%)	⬆️

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

Impacted Files	Coverage Δ
...ntity-cache-adapter-redis/src/RedisCacheAdapter.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eaab0b1...76a3256. Read the comment docs.