feat: deploy pharos and update registry

[filo87]

Closes #342

Summary

Deploy Pharos (chain id 1672) on mainnet indexing, refresh registry fetch / typing behavior, and fix a few chain/RPC details.

Changes

• Pharos (1672)

  • SELECTED_NETWORKS and PONDER_RPC_URL_1672 in environments/main.yaml and environments/main-s.yaml.
  • networkNames and endpoints in src/chains.ts (1672 → pharos; empty endpoint list for local—RPC comes from env in deployed setups).

• Registry build (scripts/fetch-registry.mjs)

  • Stable version → file slug (registryVersionToFileSlug, e.g. patch 0 dropped).
  • Normalize registry chain: deep-merge entries with version === null into the previous blob (patch-over-base).
  • Env overrides: REGISTRY_<slug>_… keys apply nested patches before writing generated files (e.g. Arbitrum startBlock in yaml via REGISTRY_v3_1_chains_42161_deployment_startBlock).
  • Keys that don’t match a known slug (e.g. REGISTRY_URL) are ignored.

• Types

  • generated/types.ts: optional verifier / verifierUrl on RegistryChain.network (aligns with registry payload).

• Chains / contracts

  • Hyperliquid QuickNode URLs: path /evm → /nanoreth.
  • chainContracts: only map contracts with a non-null address (skip placeholders).

Notes

• Deployment env adds Pharos RPC and a local registry patch for Arbitrum startBlock where upstream data lags.