Re-enable test TestProtocolVersionUpgrade

[jordanschalm]

We implemented TestProtocolVersionUpgrade as part of the original work around the Protocol KVStore, but disabled it until the corresponding smart contract change was ready to deploy to Mainnet. That smart contract change is now merged to the core-contracts feature branch, onflow/flow-core-contracts#465, to be deployed alongside EFM Recovery.

This PR re-enables the test.

• The smart contract implementation has been modified since this test was first written to emit the service event immediately (not in a system chunk)
• This PR enables require-approvals=1 and extends Chunk Data Model supports per-chunk service event mapping #6744, which implements a solution for verifying service events outside the system chunk.

[AlexHentschel]

Just came across this details while reviewing:

flow-go/state/protocol/protocol_state/kvstore/models.go

Lines 123 to 126 in a065619

	func (model *Modelv0) SetEpochExtensionViewCount(viewCount uint64) error {
	// Strictly speaking it should be perfectly fine to use a value viewCount >= model.FinalizationSafetyThreshold.
	// By using a sligtly higher value(factor of 2) we ensure that extension is big enough in practice to give operators a bigger
	// window in which a valid epoch recover event could be submitted.

technically, the operators don't submit the epoch recovery transaction - it is the human governance committee. Would you mind updating the documentation (including the typo in sligtly):

// Strictly speaking it should be perfectly fine to use a value viewCount >= model.FinalizationSafetyThreshold.
// By using a slightly higher value (factor of 2), we ensure that each extension spans a sufficiently big time 
// window for the human governance committee to submit a valid epoch recovery transaction. 

[AlexHentschel]

looks good.

[durkmurder]

🚢