test(functional): serve community shards 128 & 256 in the waku fleet

Old peers (v10.33.x) subscribe community channel filters on shards
rs/16/128 and rs/16/256, but the test fleet only served shards 32 and 64.
Those subscribes fail with 'no suitable peers found' and churn the light
client's filter manager, collaterally destabilizing the shard-32
subscription that actually carries the community message -> the light
receiver misses it and times out (flaky full-light / light-light compat
cells against v10.33.2).

Subscribe the fleet (boot-1 + store) to shards 128 and 256 as well, and
bump --num-shards-in-network to 257 so those shards validate. This is a
fleet-only change; the value is not propagated to the status-go backends
(the fleet-config scanner only emits clusterId + node ENRs), so it does
not affect how any backend derives shards.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: igor-sirotin

tests-functional/docker-compose.waku.yml

@@ -23,10 +23,12 @@ services:
       "--rest-admin",
       "--shard=32",
       "--shard=64",
+      "--shard=128",
+      "--shard=256",
       "--staticnode=/dns4/store/tcp/60002/p2p/16Uiu2HAmCDqxtfF1DwBqs7UJ4TgSnjoh6j1RtE1hhQxLLao84jLi",
       "--storenode=/dns4/store/tcp/60002/p2p/16Uiu2HAmCDqxtfF1DwBqs7UJ4TgSnjoh6j1RtE1hhQxLLao84jLi",
       "--tcp-port=60001",
-      "--num-shards-in-network=65"
+      "--num-shards-in-network=257"
     ]
     depends_on:
       - store
@@ -62,12 +64,14 @@ services:
       "--rest-admin",
       "--shard=32",
       "--shard=64",
+      "--shard=128",
+      "--shard=256",
       "--staticnode=/dns4/boot-1/tcp/60001/p2p/16Uiu2HAm3vFYHkGRURyJ6F7bwDyzMLtPEuCg4DU89T7km2u8Fjyb",
       "--store=true",
       "--store-message-db-url=sqlite:////tmp/waku-store.sqlite3",
       "--store-message-retention-policy=time:86400",
       "--tcp-port=60002",
-      "--num-shards-in-network=65"
+      "--num-shards-in-network=257"
     ]
     healthcheck:
       test: ["CMD-SHELL", "curl -X GET -H 'Content-Type: application/json' http://0.0.0.0:8645 || exit 0"]