Validate devfile with schema with matching apiVersion

[sparkoo]

Is your enhancement related to a problem? Please describe.

Currently, devfile apiVersion is validated at workspace start with hardcoded value. However, it is not validated at workspace create with proper schema. It is mandatory string parameter, so basically any value is valid. To support beta versions, we need to validate devfile with proper schema and apiVersion should be strictly validated.

Describe the solution you'd like

When creating workspace from devfile, read apiVersion value from devfile and find matching schema to validate devfile. When schema for version not found, return error.

Describe alternatives you've considered

• This solution solves just one beta version with no possibility of multiple stable versions with backward incompatible changes. For more robust solution, we will have to introduce some mechanism for different logic by given apiVersion. The solution seems sufficient for current needs.
• In case schema is not found for given apiVersion, we might want to have some default schema (1.0.0 probably) to validate. With this, we don't break already existing devfiles with invalid version (which is now basically ignored). However, having this will not force to fix invalid devfiles.

Additional context

Issue was raised up during PreviewUrl feature implementation, where we are not sure about devfile specification and we want to introduce the feature in beta version of the devfile to not break stable devfile version in the future #13945 (comment from PR #14713 (comment))

[sparkoo]

fixed by #14834

[sparkoo]

reopened because of this small patch in PR #14869

[sparkoo]

fixed #14869