API for containerd-less operation #17
Description
As discussed & 👍'd in a prior issue, there's use in having the resolver support use cases that don't involve containerd directly.
@samuelkarp and I discussed this briefly offline; my takeaway from our conversation was that we more or less agreed that a simplified standalone API would be useful. It itself would utilized by an (internal) containerd adapter that would permit friendlier use where containerd itself isn't used. This focused API would be limited to the IO operations - driven by the AWS SDK - and supporting ECR types & utilities.