CSAR block_0

["Woodlock, James" <James.Woodlock@VerizonWireless.com>]

The CSAR block_0 should have a field added for the version of the container contents (Container-Version). If the customer receives daily drops from a vendor as part of a CI/CD process, the order in which those CSARs were received could get lost.  By providing a container reference, the correct order can be re-established (i.e. 2.0 supersedes the 1.0 received; or alternatively - you need to go back to 1.1 because of problem xyz in 2.0)

TOSCA-Meta-File-Version: digit.digit
CSAR-Version: digit.digit
-> Container-Version: digit.digit  <-
Created-By: string

I realize that additional value/pairs could be added in blocks other than block_0, but by placing versions down on individual entries you don't convey the intent of the creator.  Perhaps version 2.0 of the container has a yaml script that's been reverted (2.0 -> 1.1, because of a bug) while another file has been advanced (1.1 -> 2.0) by classifying the entire container with a version you understand the creator's intent - this 2.0 version should be the replacement for 1.0