fix: preserve canonical block header hashes for Glamsterdam

[syntrust]

Summary

Preserves canonical hashes for block headers with the new fields and keeps RANDAO proofs valid.

• Upgrade Go/toolchain from 1.24.x to 1.25.14 and go-ethereum from v1.16.5 to v1.17.7; refresh the dependent modules.
• Align Docker and Go CI workflows with the new Go version.
• Preserve canonical block hashes and RANDAO proofs for headers with the new fields, while keeping Ethash hash results compatible.
• Upgrade golangci-lint GitHub Action from v3 to v9, pin golangci-lint to v2.14.0, and migrate its config to v2.
• Add offline regression coverage for L1 block refs, both RANDAO RPC paths, legacy and updated headers, and Ethash hash vectors.

Tests

The fixtures are eth_getBlockByNumber(number, false) responses retrieved from Sepolia PRCs that was cross-checked with 1RPC and Tenderly.
Block 11700000 is the pre-Glamsterdam comparison; block 11866124 reproduces issue #522.

Mining successfully with a test contract.