EPIC: ocm v1 legacy compatibility

[Skarlso]

Description
What is the goal of this epic?

Currently, relative access is available through an experimental access introduced here: open-component-model/ocm#1412

We would like to avoid doing this and introduce native local blob handling as is done by ocm v2. Ultimately, ocm v1 should be able to handle and understand component versions created by v2 to offer an easy way of existing users to migrate to v2.

User Story

As a user wanting to work with OCM, I now have the choice to work with the old OCM CLI or the new OCM CLI. When creating components with the new OCM CLI I want to be able to read the data for it with the old OCM CLI. Similarly, when working with the new OCM CLI, I want to be able to read and work with component versions created with the old OCM CLI.

Scope
List all deliverables that are part of this epic. The Epic is considered DONE if all of the below mentioned deliverables are available.

• ocm add cv from the new OCM CLI results in successfully readable Component Versions on the old OCM Commandline
• ocm get cv in the old OCM CLI can successfully read the new OCI Storage Format
• ocm-spec has a declaration of a new OCI storage format that can be accepted as alternative to the old format, which allows to reference content via OCI Image Index. This allows OCM to store localBlobs in their native layout format.

Out of Scope
List features or implementation strategies that shouldn't be considered in this iteration.