chore: dual-write all entities to Postgres + ClickHouse

Add a storage block enabling ClickHouse alongside Postgres, both default:true so
every entity syncs to both backends (Postgres serves the GraphQL API, ClickHouse
the columnar analytics store). envio auto-provisions a ClickHouse container in
dev; for an external ClickHouse set ENVIO_CLICKHOUSE_HOST / _DATABASE /
_USERNAME / _PASSWORD in .env. Verified locally: all 26 entity tables mirrored;
PegKeeper data identical in both (3 keepers / 382 actions); a ClickHouse
aggregation confirms keepers provide above peg (avg 1.0024) and withdraw below
(avg 0.9998).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: moose-code

config.yaml

@@ -1,6 +1,21 @@
 # yaml-language-server: $schema=./node_modules/envio/evm.schema.json
 name: curve-crypto-pools
 
+# Storage backends. Every entity is written to BOTH Postgres (serves the GraphQL
+# API) and ClickHouse (columnar store for analytics). Both backends are marked
+# `default: true` so all entities without an explicit @storage directive land in
+# both — note that enabling ClickHouse flips Postgres's implicit default to false,
+# so Postgres must be set explicitly here. Per-entity routing is also possible via
+# an `@storage` directive in schema.graphql; omitted because we want full coverage.
+# ClickHouse connection is read from .env:
+#   ENVIO_CLICKHOUSE_HOST, ENVIO_CLICKHOUSE_DATABASE,
+#   ENVIO_CLICKHOUSE_USERNAME, ENVIO_CLICKHOUSE_PASSWORD
+storage:
+  postgres:
+    default: true
+  clickhouse:
+    default: true
+
 contracts:
   - name: TricryptoFactoryNG
     events: