Build OCI artifacts and save to the registry

[nabokihms]

Before proceeding

• I didn't find a similar issue

Problem

Currently, there is no functionality in werf to save images as OCI artifacts during the build stage.
Some artifacts are required to be saved in the container registry for further distribution, e.g., to build and distribute binaries.

Solution (if you have one)

Introduce the capability to save images as OCI artifacts during the build process in werf. This feature would allow users to produce OCI-compliant artifacts directly from their builds, enhancing interoperability and compatibility with other container tools and platforms.

The example of the possible werf.yaml to show the idea.

image: my-app
artifact: true
git:
- add: /
  to: /src
shell:
  install:
  - go build /src/main.go -o /my-app
---
image: my-app-binary
oci: true
fromArtifact: my-app
filePath: /my-app
mediatype: application/vnd.my-company.golang.binary.content.v1

As a result, the /my-app binary from the my-app artifact will be uploaded to the container registry.

Additional information

By enabling the option to save images as OCI artifacts, werf users can benefit from improved portability and standardized image distribution. OCI artifacts offer advantages such as reduced complexity, increased security, and better support for multi-platform environments. This enhancement aligns with industry best practices and enhances the overall usability and versatility of the werf tool.

For more information about OCI (Open Container Initiative) standards, please refer to the official OCI website: Open Container Initiative.