Remove per-package ImageOption definitions since they are not useful

Previous commits changed function signatures like
func NewImage(repoName string, dockerClient DockerClient, ops ...imgutil.ImageOption) (*Image, error)
to expect imgutil.ImageOption instead of remote.ImageOption or whatever

imgutil.ImageOption and remote.ImageOption are interchangeable when passed into the function
but the signature needs a specific type

Signed-off-by: Natalie Arellano <narellano@vmware.com>

layout/options.go

@@ -8,8 +8,6 @@ import (
  "github.com/buildpacks/imgutil"
 )
 
-type ImageOption func(*imgutil.ImageOptions)
-
 // FromBaseImageInstance loads the provided image as the manifest, config, and layers for the working image.
 // If the image is not found, it does nothing.
 func FromBaseImageInstance(image v1.Image) func(*imgutil.ImageOptions) {

local/options.go

@@ -8,8 +8,6 @@ import (
  "github.com/buildpacks/imgutil"
 )
 
-type ImageOption func(o *imgutil.ImageOptions)
-
 // FIXME: the following functions are defined in this package for backwards compatibility,
 // and should eventually be deprecated.
 

remote/options.go

@@ -8,8 +8,6 @@ import (
  "github.com/buildpacks/imgutil"
 )
 
-type ImageOption func(o *imgutil.ImageOptions)
-
 // AddEmptyLayerOnSave adds an empty layer before saving if the image has no layers at all.
 // This option is useful when exporting to registries that do not allow saving an image without layers,
 // for example: gcr.io.