[Protocol Versioning] Implement Service Events on Protocol Layer (flow-go only) #7144

Overarching Product Goal

This issue is part of Epic #6999. The overall goal is to evolve Versioning of Execution Stack to use the Dynamic Protocol State, and subsequently employ this versioning information for

1. coordinating EN HCUs (see Flip 298 for more context on product relevance and impact)
2. the ANs to supports script execution across breaking HCU version boundaries (see OKR description for more context on product relevance and impact)

This issue is part of 1.

Detailed Task Description

Context: we previously implemented the Service Events (see issue #7144) for scheduling a change to the Execution Stack parameters. As those Service Events are bases on human inputs, we decided to specify rules when to accept or reject such Service Event (issue #7143) wanting to update the Execution Stack parameters.

• We implement two separate service events
  1. One Service Event carrying the new values for CadenceComponentVersion and ExecutionComponentVersion
  2. One Service Event carrying the new values for ExecutionMeteringParameters (includes ExecutionEffortParameters , ExecutionMemoryParameters, and ExecutionMemoryLimit)

Implement Service Events on Protocol Layer (flow-go) only (we have separate issue for updating the smart contracts)

Further Reading:

• section 📝 2025-03-04 Review of implementation proposal in notion doc Execution State Parameters in the Dynamic Protocol State