Devfile 2.2.x support

[michael-valdron]

/kind enhancement

Which area this feature is related to?

/area api
/area library

Issue details

With the release of devfile 2.2.0, the devfile spec brings a fair amount of new features, such as outerloop and multi version support. With this in mind, it is important to the consumers of alizer to have support for 2.2.x schema versions.

Related Issues

UPDATE: @thepetk
As this is transformed in an EPIC I'm including all children issues here:

• Create Proposal for 2.2.x devfile version support #225
• Add min-version and max-version CLI arguments #226
• Add deployment-scope CLI argument #227

[thepetk]

For this case, we can:

• Include an extra field in alizer response (version) which will include the version of the devfile.
• Make the selection process configurable and if someone passes a version alizer should detect devfiles from this version or older.
  WDYT?

[thepetk]

As this new feature requires a fair amount of updates I'll draft a proposal and share it with a PR in order to pick the best solution for this issue.

Target date: 09 June 2023

[thepetk]

We are still working on a proposal for this feature.

[thepetk]

The final refinements of the proposal are about to be done and a proper PR will be added

[thepetk]

Still working on the proposal, expecting to have a PR ready until 2nd of June. I've updated the target date

[elsony]

Changing this to an Epic since it will have child issues for doing the implementations on the proposal

[thepetk]

I've added all related tasks to this epic

[thepetk]

closing in favor of devfile/api#1170