Fix --l2-anytrust: bump pinned nitro image and use the renamed AnyTrust binaries

[pmikolajczyk41]

Problem

./test-node.bash --l2-anytrust has been broken: all three AnyTrust containers exit(1) at startup.

Cause

a47a079e7 [config] Rename DAS to AnyTrust (#4142) (nitro, 2025-12-18) did two things at once, and the testnode only followed one:

	testnode state	consequence
Server config gained top-level parent-chain	✅ already migrated (config.ts, Dec 2025)	pinned v3.9.6 rejects it
daserver→anytrustserver, datool→anytrusttool	❌ old names	post-rename images have no daserver
NITRO_NODE_VERSION pin	❌ v3.9.6-91bf578 (pre-rename)	root cause of both

Half-migrated: it generates the new config but pins an image too old to parse it, while its entrypoints name binaries too old for any current image. Broken in both directions. The observed failure:

Fatal configuration error: 1 error(s) decoding:
* '' has invalid keys: parent-chain

Changes

• test-node.bash — pin offchainlabs/nitro-node:v3.11.3-beb2108 (rename landed in v3.11.0; verified this tag contains anytrustserver/anytrusttool)
• docker-compose.yaml — 4 entrypoints to the new binary names
• test-node.bash — inline datool dumpkeyset → anytrusttool
• scripts/config.ts — node DA config node.data-availability → node.da.anytrust (separate commit)

The compose service is still named datool, so the 9 docker compose run … datool call sites are untouched.

config.ts:550,579 are deliberately unchanged — those are the server config, where top-level data-availability is still correct.

Verified

--init-force --l2-anytrust: all three containers Up; Added AnyTrust writer; L2 tx status: 1; 118 payloads stored in each of committee-a, committee-b and the mirror; zero DEPRECATED lines.

Note for reviewers

This bumps the default nitro image by two minor versions, so it affects every testnode user, not just AnyTrust.

---

closes NIT-5547