Implement upgrade mechanism for Chunk ServiceEventCount field

[jordanschalm]

Context

#6744 contains discussion for different strategies for deploying the ServiceEventCount field safely. The source of truth for this decision will be tracked in the Notion document.

This issue is to implement the business logic required for upgrade safety, as described here.

Definition of Done

(see Notion document for description of sv/pv/dv version shorthands). Let V1 be the activation view of the protocol version upgrade.

• ENs upgraded to sv2 will:
  • produce dv2.1 ExecutionResults for blocks with views < V1
  • produce dv2.2 ExecutionResults for blocks with views >= V1
• SNs upgraded to sv2 will:
  • accept only dv2.1 ExecutionResults for blocks with views < V1
  • accept only dv2.2 ExecutionResults for blocks with views >= V1
• VNs do not need additional logic, as they rely on SNs "gating entry" of results into blocks.