[FAB-11872] Decouple MetadataLifecycle from 1.3 release

The new lifecycle work will not be available in the 1.3 release and so the
MetadataLifecycle capability must be decoupled with the "V1_3" application
capability of a channel.

Change-Id: Ia75a3165e4d6b6f5a12c41ef9204670f518b3f68
Signed-off-by: Alessandro Sorniotti <ale.linux@sopit.net>

common/capabilities/application.go

@@ -100,7 +100,7 @@ func (ap *ApplicationProvider) V1_3Validation() bool {
 // v1.0/v1.1/v1.2 lifecycle, or whether it should use the newer per channel peer local chaincode
 // metadata package approach planned for release with Fabric v1.3
 func (ap *ApplicationProvider) MetadataLifecycle() bool {
-	return ap.v13
+	return false
 }
 
 // KeyLevelEndorsement returns true if this channel supports endorsement

common/capabilities/application_test.go

@@ -52,7 +52,6 @@ func TestApplicationV13(t *testing.T) {
 	assert.True(t, ap.V1_2Validation())
 	assert.True(t, ap.V1_3Validation())
 	assert.True(t, ap.KeyLevelEndorsement())
-	assert.True(t, ap.MetadataLifecycle())
 	assert.True(t, ap.ACLs())
 	assert.True(t, ap.CollectionUpgrade())
 	assert.True(t, ap.PrivateChannelData())