feat: add and use chain.scripts.chainRpcReady

[michaelfig]

This PR consolidates all the different ways of checking if a chain node's RPC service is ready to use.

Documentation, scripts, and examples have been updated accordingly.

The Agoric readinessProbe now just uses the defaults. I've verified that properly waiting for RPC to become ready (instead of restarting the pod's faucet and hitting backoff) has reduced the time needed to boot up agoriclocal-genesis-0 on my machine from 14 minutes down to 6 minutes.

[Copilot]

Pull Request Overview

This PR consolidates the various methods of checking if a chain node's RPC service is ready by introducing a dedicated chainRpcReady script.

• Integrates the chainRpcReady script configuration in values.yaml and values.schema.json.
• Updates the readiness probes in validator.yaml and genesis.yaml to use the chainRpcReady script via exec commands.
• Updates defaults.yaml and documentation to reflect the new approach.

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
starship/charts/devnet/values.yaml	Adds commented configuration for chainRpcReady script.
starship/charts/devnet/values.schema.json	Introduces a new schema object to validate the chainRpcReady configuration.
starship/charts/devnet/templates/chains/cosmos/validator.yaml	Replaces HTTP GET readiness check with an exec command calling chainRpcReady script.
starship/charts/devnet/templates/chains/cosmos/genesis.yaml	Replaces HTTP GET & custom loop with exec commands for the chainRpcReady script and mounts the /scripts volume.
starship/charts/devnet/scripts/default/chain-rpc-ready.sh	Provides the new script that determines if the RPC service is ready.
starship/charts/devnet/defaults.yaml	Updates the default scripts to include chainRpcReady.
docs/config/chains.mdx	Updates documentation to include details for the chainRpcReady script.

[Copilot]

Assuming that '.earliest_block_height' and '.latest_block_height' are numeric values, if these values are returned as strings by the API, consider using 'tonumber' within jq to ensure a proper numerical comparison.

Suggested change

	if [ "$(echo "$json" | jq -r '.result.sync_info | (.earliest_block_height < .latest_block_height)')" != true ]; then
	if [ "$(echo "$json" | jq -r '.result.sync_info | (.earliest_block_height | tonumber) < (.latest_block_height | tonumber)')" != true ]; then

[Anmol1696]

LGTM