Etherlink/Revm: rely on a propagated specid instead of hardcoding configuration
Context
As the MR title says, we relied on a hardcoded specid, now we properly propagate the specid. I removed the previous "hack" from !18458 (merged) as it wasn't really clean to do that.
The MR also contains an optimisation (first commit) which allows to remove the hack. The hack was "legit" but introduced for the wrong reason in our case.
The MR is based on !18459 (merged) to avoid conflicts.
More context in !18460 (comment 2582200605).
Edited by Rodi-Can Bozman