Provide API for deployment resources that product and push build artifacts

When building deployment pipelines, there's a frequent requirement to model the following set of behaviors across multiple scenarios:

- Build assets for a compute resource (docker build, npm build, dotnet publish)
- Manage these assets in local and CI/CD-based pipelines (e.g. avoid building assets in release pipelines)
- Push these assets to some sort of registry (CDN, container registry, etc.)

Our current deployment process is optimized for resources that get built as Docker images (although we do have feature gaps here).

We should consider modeling this for non-Docker image based resources as well.