v0.4.0 — the image can now reach the chain

v0.4.0 — the image can now reach the chain

UPGRADE IMMEDIATELY. Every previous 0.x image sets no weights at all: it
fetches and verifies correctly, then fails at [chain] open failed on every
tick, while the container reports healthy the whole time.

Cause: bittensor 9.x pins scalecodec but leaves async-substrate-interface
open at the top, and asi 2.0 replaced scalecodec with cyscale claiming the
same namespace - so the two refuse to coexist and bittensor raises at
import. No configuration of bittensor 9.x works against the current finney
runtime. Moved to bittensor 10.5, which completed that migration and bounds
asi itself, and dropped substrate-interface, which was the last thing
pulling scalecodec back in.

Verified in a clean install against live finney: 256 hotkeys read from
netuid 53 and a burn vector resolving to uid 229.

Known issue, not fixed here: the pinned Watchtower image speaks a Docker API
version newer daemons refuse, and crash-loops. If your Watchtower is
restarting, this release will not reach you automatically - pull it by hand:

docker compose --env-file .env.validator -f docker/docker-compose.validator.yml pull
docker compose --env-file .env.validator -f docker/docker-compose.validator.yml up -d