Allow to define blueprint artifacts as part of the blueprint entity itself

In order to simplify the creation of blueprint objects it would be great if one could have the blueprint artifacts defined within the spec of the Blueprint itself.

As far as I've understood, per the current api spec, the blueprint entity and the artifact entity are treated as completely independent resources (although the Artifacts are actually child objects of a blueprint). It would make sense, in my view, that the blueprint entity had an optional property consisting on the list of artifacts applicable to that blueprint as a blueprint without artifacts would only be able to define resource groups as per the current api spec and one would need to define the artifacts in subsequent api operations one per each artifact to add.

Auto generated clients from this api spec will then inherit the above mentioned limitations.

No file or test is named in the issue. Start by reviewing the current blueprint and artifact resource definitions in the API specification, then determine how an optional artifact list should be represented within Blueprint and reflected by generated clients. Done means the specification supports creating a blueprint with its artifacts while preserving blueprints without artifacts.

Written by the indexing model from the issue text.