Different VM disk size when pulling from registry

[evanburkeyhl]

When pulling images pushed to Github container registry, the disk utilization is the maximum size of the disk instead of the actual size. I hope I'm just doing something wrong

Reproduction

1. Start with a vanilla image from https://github.com/cirruslabs/macos-image-templates
2. Create a clone and modify it for our specific needs. Disk sizes look like this on my local machine after customizations

   local  monterey   22   stopped
   local  sonoma      23   stopped
   local  ventura       16   stopped

3. Upload the clones to Github Package Registry with tart push
4. Use tart pull to clone machines to CI VM host
5. Disk sizes on the host are maximum size

   local  monterey  40   stopped
   local  sonoma     50   stopped
   local  ventura      80   stopped

   I verified with our IT team that the disk utilization on the host grew ~170GB after pulling these 3 images.

[edigaryev]

Please check out the new 2.4.0 release, it should create smaller disks on tart pull by using sparse files.