[FAB-9870] Use CollectionUpgrade Capab. in lscc

Currently, lscc uses `V1_2Validation` capability to check
whether collection upgrades can be allowed. However, the
`V1_2Validation` is defined for vscc validation and hence,
this CR replace `V1_2Validation` with `CollectionUpgrade`
capability.

Change-Id: I97021fb7323333879a0f77d6fc2323d93aedb1a0
Signed-off-by: senthil <cendhu@gmail.com>

Author: cendhu

core/scc/lscc/lscc.go

@@ -596,10 +596,7 @@ func (lscc *lifeCycleSysCC) executeUpgrade(stub shim.ChaincodeStubInterface, cha
 		logger.Panicf("programming error, non-existent appplication config for channel '%s'", chainName)
 	}
 
-	// TODO: Instead of V1_2Validation(), we should be using something like CollectionUpdate().
-	// For time being, V1_2Validation() is used. Need to submit a separate CR to introduce a
-	// new capability named CollectionUpdate.
-	if ac.Capabilities().V1_2Validation() {
+	if ac.Capabilities().CollectionUpgrade() {
 		err = lscc.putChaincodeCollectionData(stub, cdfs, collectionConfigBytes)
 		if err != nil {
 			return nil, err

core/scc/lscc/lscc_test.go

@@ -515,7 +515,7 @@ func TestUpgrade(t *testing.T) {
 		ApplicationConfigRv: &config.MockApplication{
 			CapabilitiesRv: &config.MockApplicationCapabilities{
 				PrivateChannelDataRv: true,
-				V1_2ValidationRv:     true,
+				CollectionUpgradeRv:  true,
 			},
 		},
 	}).NewSystemChaincodeProvider().(*mscc.MocksccProviderImpl)