[Protocol Versioning] Governance Smart Contracts to emit the newly defined Service Events

[AlexHentschel]

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: In the previous issue #7144, we have defined service events from the perspective of the protocol, that are allowed to change the Execution Parameters in the Dynamic Protocol State.

Now, we need to modify Governance Smart Contracts to emit the newly defined Service Events:

• Governance Smart Contract Updates so they can emit

  1. One type of Service Event carrying the new values for CadenceComponentVersion and ExecutionComponentVersion
  2. Another type of Service Event carrying the new values for ExecutionMeteringParameters (includes ExecutionEffortParameters , ExecutionMemoryParameters, and ExecutionMemoryLimit)

• It would probably be the most consistent (but not strictly necessary) to structure the governance transactions accordingly.

  We might desire tooling for creating those governance transaction.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.