Devfile 2.2.x support for Alizer

[thepetk]

/kind enhancement
/kind epic

Which area this feature is related to?

/area alizer

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 redhat-developer/alizer#225
• Add min-version and max-version params to alizer CLI #1171
• Minor improvments on Alizer's min/max version CLI arguments #1182

[thepetk]

Follow comments from old (pre-migration) issue here: redhat-developer/alizer#159

[thepetk]

I've gone through the newly introduced solution for #1171 where we have included --min-version and --max-version. I think two additions could be made here for better user experience:

• As version is used both on the schemaVersion and the version of stack in the devfiles, we might want to make a small rename to the CLI param to --min-schema-version and --max-schema-version.
• We could include the versions list returned from the registry API so we can have a response:

$ ./alizer devfile --min-schema-version 2.2.0 --max-schema-version 2.2.0 ~/github/thepetk/go-ps-script

[
	{
		"Name": "go",
		"Language": "Go",
		"ProjectType": "Go",
		"Tags": [
			"Go"
		],
		"Versions": [
			{
				"SchemaVersion": "2.2.0",
				"Version": "1.1.1",
				"Default": false
			},
			{
				"SchemaVersion": "2.2.0",
				"Version": "1.1.0",
				"Default": false
			}
		]
	}
]

cc @mike-hoang @elsony

[thepetk]

Created and added to epic the #1182

[thepetk]

The last item which is still opened #1172 remains blocked and the EPIC is currently under TODO

[thepetk]

Moving #1172 outside of the EPIC in order to be treated as a standalone task for Q1/2024. As a result the current EPIC is completed