fix: fix cached: prefix in Scan CLI

[JeremyTubongbanua]

What I did

Checked for isCached metadata and prepend cached: to the key name if isCached==true

[gkc]

LGTM

[gkc]

LGTM

@JeremyTubongbanua What's your plan for the scan impl itself?

[JeremyTubongbanua]

LGTM

@JeremyTubongbanua What's your plan for the scan impl itself?

The getAtKeys() method returns a List<AtKey>, I don't think there's much I could do unless I modify the .toString() in AtKey

[gkc]

Yeah it's a bit tricky. Here's the way I think all of this should work: cached should not be a part of the key name. When @bob creates data which they share with @alice, and @alice secondary decides to cache that data (for whatever reason), then I believe there is zero value in prepending 'cached:' to the key name, since the very fact that @bob-owned data is stored on @alice's secondary shows that it is cached.

@nickelskevin what do you think about this? This is relevant given our recent & ongoing conversation about overhauling caching behaviour generally