guard update frequency in contract

[goastler]

No description provided.

[goastler]

Due to how the seed updates work and how configuration changes are recorded for replay capability, we need to limit the frequency of updates to certain fields.

E.g. we record every time a dapp becomes active/inactive. If a dapp can call the dapp_update fn as much as they like, they can spam the contract as each update would be recorded in order to do a replay in the future. We need to limit this.

This is a good security mechanism to have in general for any field, as no field should be being updated multiple times per block, really.