Description
To be able to perform reach feature parity with the old ocm cli, we also need to be able to transfer resources with an access type of ociArtifact.

To do this within the transformation specification, we need:

• ociArtifact download transformer
• ociArtifact upload transformer
• adjustment of the "Generiererich" (aka the transfer command) to include downloaders and uploaders for each oci artifact in a component (maybe depending on a flag - see note below).

Note
The legacy ocm cli had default uploaders (aka blob handlers) registered for ociArtifacts. So, during ocm transfer between OCIRegistry ocm repositories, OCIArtifacts were uploaded by default (I think). Do we want to adopt this behavior? Do we want to have a ocm transfer component flag to determine this behavior? Do we want some other mechanism?

Done Criteria

• ocm transfer component can transfer ociArtifacts
• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Enduser Documentation updated (if applicable)
• Internal technical Documentation created/updated (if applicable)
• Successful demonstration in Review