Add new CRDs to support root resource mapping

[LeiQL]

• Add new CRDs: instanceContainer, solutionContainer, targetContainer, catalogContainer, campaignContainer
• Add rootResource and version in solution, target, instance, catalog, campaign to support liquid property mapping

[Haishi2016]

Just to double-check, the plan is to add these CRDs first and then do renaming later?

[LeiQL]

t to double-check, the plan is to add these CRDs first and then do renaming

@Haishi2016 renaming is not scheduled before private preview. We can add a task for renaming and schedule it based on priorities. And FYI, the support of object reference (myapp:latest, myapp:v1-0) is under development and testing. I will have PRs for the support of labelling and reference.

[msftcoderdjw]

This PR introduces the first part of versioning changes - modify data model. I am OK with this change. Team can review and drop more comments if needed. One more suggestion is maybe we don't need to keep rootResource and version in Spec. It is better to keep them in metadata like metadata.name.

[LeiQL]

This PR introduces the first part of versioning changes - modify data model. I am OK with this change. Team can review and drop more comments if needed. One more suggestion is maybe we don't need to keep rootResource and version in Spec. It is better to keep them in metadata like metadata.name.

metadata field liquid mapping only mentions metdata.name mapping. It needs to be investigated whether other fields in metadata can be mapped via liquid. This can be scheduled post private preview.

[LeiQL]

@Haishi2016 @msftcoderdjw do we have any other concerns or questions on this PR?

[Haishi2016]

I'm fine with this PR, with understanding that 1) we are going to refactor the version and rootresource attributes out of spec in the future; 2) we need to bring similar changes to other object types like devices, skills and models; 3) we are going to do renaming of objects in upcoming PRs.