Align standalone NFT worker Erlang node naming

[JOY (JOY)]

Summary

• keep the optional standalone NFT media worker on the same short-name distribution mode as the backend from PR Fix NFT media RPC node discovery #119
• replace the worker IP node name with its stable Compose service name

Why this follow-up is required

PR #119 fixed the production backend RPC failure by changing producer@backend to Erlang short-name mode. The repository's default Compose stack also starts a standalone NFT media worker, which still used long-name mode and worker@0.0.0.0. Short-name and long-name Erlang nodes cannot connect, so the worker must match the backend.

Validation

• python scripts/validate-blockscout-env-parity.py
• git diff --check
• docker compose config resolves backend and worker to matching sname mode
• Erlang runtime accepted worker@nft_media_handler_probe on the Testnet Compose network
• independent review found the mismatch as P1; the worker was updated and re-review found no actionable issues

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.