Support setting zkapp limit in orchestrator

[georgeee]

Bonus: ability to check that X% of stake were updated.

Explain your changes:

• Adds a command to Orchestrator to allow setting zkapp limit on nodes in the test environment
• Adds a command that (combined with existing slots-won command) allows to check that at least X% of stake were affected by the soft limit upgrade

Explain how you tested your changes:

• Tested on the large cluster:
  • set limit to 23 zkapp txs/min

    {"action":"discovery","params":{"offsetMin":15}}
    {"action":"set-zkapp-soft-limit","params":{"limit":23,"nodes":{"type":"output","step":-1,"name":"participant"}}}
    {"action":"slots-won","params":{"nodes":{"type":"output","step":-1,"name":"participant"}}}
    {"action":"slots-covered-check","params":{"threshold":0.6,"slotsWon":{"type":"output","step":-1,"name":"slotsWon"}}}
    

  • switch on the zkapp transaction sending
  • unset the limit

    {"action":"discovery","params":{"offsetMin":15}}
    {"action":"set-zkapp-soft-limit","params":{"limit":null,"nodes":{"type":"output","step":-1,"name":"participant"}}}
    {"action":"slots-won","params":{"nodes":{"type":"output","step":-1,"name":"participant"}}}
    {"action":"slots-covered-check","params":{"threshold":0.6,"slotsWon":{"type":"output","step":-1,"name":"slotsWon"}}}
    

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? None

[georgeee]

!ci-build-me

[georgeee]

!ci-build-me

[georgeee]

!ci-build-me

[mrmr1993]

!approved-for-mainnet