system: use containers/storage for LCOW validation

[flouthoc]

Newer versions of github.com/docker/docker does not supports the LCOW validation functions which imagebuilder uses hence move them to a local package of imagebuilder and drop dependency on
github.com/docker/docker/pkg/system

Alternative solution: refactor imagebuilder to stop using LCOWSupported()

Closes and helps in: containers/buildah#4555

[flouthoc]

@nalind @rhatdan I think moby has dropped LCOW check and does not contain any public API for it, hence we can move it to imagebuilder or refactor imagebuilder so we can also drop LCOW support but I am not sure if anybody is still using logic for the former one hence a safer bet is to move LCOW checks here.

[nalind]

That logic is still around in the containers/storage pkg/system. Switch it to using that, it's less code to carry around in here.

[flouthoc]

I see some overlapping work here: #245 @nalind let me know if i can close this.

[nalind]

/lgtm
/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc, nalind

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nalind]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@flouthoc: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[nalind]

/hold cancel

[nalind]

/override "Travis CI - Pull Request"

[openshift-ci]

@nalind: Overrode contexts on behalf of nalind: Travis CI - Pull Request

In response to this:

/override "Travis CI - Pull Request"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.