RFE: Allow api return code of errors

[camilamacedo86]

Describe the problem you need a feature to resolve.

Currently, we are able to validate the bundle against scenarios to check if they are not ok to be published and then, we receive a list of errors and/or warnings. However, we need to grep by text to know the kind of errors and warnings that came out to do specific actions according to them.

Describe the solution you'd like.

I'd like to see the implementation of the api allowing us to define code for errors. In this way, we could check by these codes instead of grepping a text that can be easily changed/improved. One example of what is expected here is the HTTP implementation with code errors which allow us to easily check them.

[kevinrizza]

This to me seems like a reasonable change to include in the existing validation spec. I do think it would involve us coming up with a very explicit spec of the hierarchy and type of validation errors, which does not currently exist, even before we could create such a mapping.

I also want to point out that this spec would only apply to registry+v1 bundle images, and in the future when we support other bundle types we will probably need to have a separate spec and validation mechanism.