Improve dmverity-vhd -d performance (#2089)

The current implementation of dmverity-vhd -d has to make one of the
following tradeoffs:

Runtime: By default this option calls the docker daemon to fetch the
entire image for each layer as it doesn't provide an endpoint to get
a specific layer
Memory: The user can include a -b option that makes this call buffered,
keeping the image in memory the whole time, this is much faster but
at the cost of keeping the whole image in memory, which is a problem
with runners with low memory

#2086 Proposed a new tradeoff of disk space, by saving the image to
disk and accessing the layers locally, this is a problem for runners with
smaller disks as the image is stored twice.

This solution makes a single request to the docker daemon, and
processes both the layer hashes and the manifest to assign layer
numbers in a single pass, making it performant in all three aspects.

---------

Signed-off-by: Dominic Ayre <[email protected]>
Signed-off-by: Dominic Ayre <[email protected]>

go.mod

@@ -16,6 +16,7 @@ require (
 	github.com/containerd/protobuild v0.3.0
 	github.com/containerd/ttrpc v1.2.3
 	github.com/containerd/typeurl/v2 v2.1.1
+	github.com/docker/docker v24.0.9+incompatible
 	github.com/google/go-cmp v0.6.0
 	github.com/google/go-containerregistry v0.19.1
 	github.com/josephspurrier/goversioninfo v1.4.0
@@ -56,7 +57,6 @@ require (
 	github.com/decred/dcrd/dcrec/secp256k1/v4 v4.2.0 // indirect
 	github.com/docker/cli v24.0.0+incompatible // indirect
 	github.com/docker/distribution v2.8.2+incompatible // indirect
-	github.com/docker/docker v24.0.9+incompatible // indirect
 	github.com/docker/docker-credential-helpers v0.7.0 // indirect
 	github.com/docker/go-connections v0.4.0 // indirect
 	github.com/docker/go-events v0.0.0-20190806004212-e31b211e4f1c // indirect