Fix restorer target update

[natalieparellano]

When we instantiate the remote image for the purpose of checking target data, we should provide "from base image" so that we don't end up returning data for an empty image

[natalieparellano]

TDD notes...

Failing test (prior to code changes): https://github.com/buildpacks/lifecycle/actions/runs/5660989254/job/15337920259#step:5:10277

Note that 03cbce912ef1a8a658f73c660ab9c539d67188622f00b15c4f15b89b884f0e10 is a "special" SHA for empty images - e.g.,

	image, _ := remote.NewImage("busybox", authn.DefaultKeychain)
	fmt.Println(image.Identifier())

prints index.docker.io/library/busybox@sha256:03cbce912ef1a8a658f73c660ab9c539d67188622f00b15c4f15b89b884f0e10.

Oddly, I couldn't get this to fail locally. Locally, the run image reference returned is something like 192.168.1.43:64606/some-read-only-run-image-dtakgtkcmh@sha256:d0143fdc9f75c98c264f019d1c690bb17845d4b514ce1a44555eef3794ce3980

I'm assuming this has something to do with oddities around the test registry, but I'm not sure

[joe-kimmel-vmw]

LGTM in the sense that unit tests don't lie, but it's a little mysterious.

[natalieparellano]

LGTM in the sense that unit tests don't lie, but it's a little mysterious.

There was something wrong with my local setup, I can see the failing tests now. All good!