feat(sequencer): Add new validator update action

[ethanoroshiba]

Summary

Added new action ValidatorUpdateV2, which houses the same functionality as ValidatorUpdate but now includes a name field.

Background

Previously, validator names were not stored app-side, and names could only be set in CometBFT genesis.

Changes

• Added ValidatorUpdateV2 action to protos and core.
• Restricted validator name to 32 characters when converting from on-wire format.
• Added ValidatorNames struct, which contains address <> name key-value pairs.
• Added storage keys, value impls, snapshots, and state read/write methods for ValidatorNames.
• Added new ABCI query for validator name, accepting address as a parameter.
• Edited ValidatorSet to use insert instead of push_update so that it doesn't imply any ordering.

Testing

• Snapshot tests added for new VALIDATOR_NAMES storage key
• Unit tests for new state read/write methods
• Unit tests that new ABCI query works as expected
• Unit test for ABCI query router to validator_name_request.
• App execution test for ValidatorUpdateV2.
• Added ValidatorUpdateV2 to app_execute_transaction_with_every_action.

Related Issues

closes #1590

[ethanoroshiba]

Should we explicitly check against chars(), or is 32 bytes fine?

[noot]

would prefer to store each validator name in a separate storage entry so we don't have to fetch every single validator name just to update one name. then to get all the names, you can use a prefix iterator to return a stream, as all validator names will be stored after one prefix (eg. keys are of the form valname/<address> where valname is the storage prefix).

see example here:

astria/crates/astria-sequencer/src/fees/state_ext.rs

Line 371 in 3cabf59

fn allowed_fee_assets(&self) -> AllowedFeeAssetsStream<Self::PrefixKeysStream> {

[ethanoroshiba]

Thanks for this catch! Done in a7a64af