Add labels to cache volumes

[dwillist]

Signed-off-by: dwillist dthornton@vmware.com

Summary

Adds human readable info to pack volumes.

Output

previously pack volumes were named with a sha256 and had the form <sha256>.<prefix>
now they will be of the form
pack-cache-<repo>-<name>-<tag>-sha256.<prefix>

Before

After

Documentation

• Should this change be documented?
  • Yes, see #___
  • [ x ] No

Resolves #317

[codecov]

Codecov Report

Merging #1039 (b48bbe1) into main (ddaff10) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1039      +/-   ##
==========================================
+ Coverage   80.22%   80.24%   +0.03%     
==========================================
  Files         130      130              
  Lines        7989     7993       +4     
==========================================
+ Hits         6408     6413       +5     
+ Misses       1161     1160       -1     
  Partials      420      420              

Flag	Coverage Δ
os_linux	79.55% <100.00%> (+0.05%)	⬆️
os_macos	?
os_windows	80.15% <100.00%> (+0.05%)	⬆️
unit	79.55% <100.00%> (-0.04%)	⬇️

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

[dfreilich]

Before:

 $  docker volume ls
DRIVER    VOLUME NAME
local     pack-cache-b07b36ffb1de.build
local     pack-cache-b07b36ffb1de.launch

After:

local     pack-cache-dfreilich_test-noop_latest-4e450adbfda1.build # ghcr publish
local     pack-cache-dfreilich_test-noop_latest-a17094201004.build # docker publish
local     pack-cache-library_test-noop_latest-b07b36ffb1de.build # local docker build
local     pack-cache-library_test-noop_latest-b07b36ffb1de.launch. #local docker build

Overall, this definitely seems to do what it set out to do. I have some quibbles about the presentation (library isn't super clear, and perhaps we should keep the entire registry string), but overall I think it's definitely a great start, and we can iterate on it as we need.