Governor/custom reset release timer delay

[pleasew8t]

Description

This pull request adds an additional parameter to the governor-reset-release-timer admin command, num_days. num_days allows operators to specify the number of days a pending VAA's release needs to be reset to. This allows operators to specify delays larger than the current default (24 hours).

The parameter is optional and, if omitted, will default to the current implementation's reset value of 24 hours. If specified, the parameter may not be less than 1 day, or exceed 7 days, otherwise the release time reset will fail.

Use-case

This feature is particularly useful in scenarios where follow-up delays beyond 24 hours are anticipated, but participation by guardians cannot be guaranteed. For example, a VAA gets enqueued by the governor (imposing a delay of 24 hours), but some guardians opt to delay the VAA's release even further.

If one of these guardians recognizes that they will not be available to reset the delay over the course of the following two days, the said guardian could use the governor-reset-release-timer command to proactively delay the release to 2, or even 3, days.

Summary of code changes

• Updated the ClientChainGovernorResetReleaseTimerCmd admin client command
• Added a num_days field to the ChainGovernorResetReleaseTimerRequest protobuf message
• Updated the ChainGovernorResetReleaseTimer RPC service
• Added the TestNumDaysForReleaseTimerReset governor test

[SEJeff]

Some minor nits, but this looks pretty good from a cursory overview.

[SEJeff]

If you submit this to the main wormhole repo, I will ✅