collections config for fixed asset private data should set an explicit endorsement policy

[davidkel]

As the transaction implementation and private data collection is designed to only be used by Org1 we need to set the endorsement policy explicitly on the collections config otherwise it will default to the chaincode endorsement policy and if that is left to the default is likely to result in sending data to multiple orgs. As this uses private data we would not want to be sending transient private data to any other org than the one specified. So we should add to the collections-config

      "endorsementPolicy": {
        "signaturePolicy": "OR('Org1MSP.member')"
      }

so the collections config should look like

[
    {
      "name": "CollectionOne",
      "policy": "OR('Org1MSP.member')",
      "requiredPeerCount": 0,
      "maxPeerCount": 1,
      "blockToLive": 0,
      "memberOnlyRead": false,
      "endorsementPolicy": {
        "signaturePolicy": "OR('Org1MSP.member')"
      }
    }
]