Add ETC Spiral EVM configuration

[diega]

PR description

During the last ETC network upgrade, Besu nodes got stalled because, inadvertently, EIP-4399 was included instead of omitted.

For the future, we'll also test omissions to the protocol and not only additions.

[github-actions]

• I thought about documentation and added the doc-change-required label to this PR if updates are required.
• I thought about the changelog and included a changelog update if required.
• If my PR includes database changes (e.g. KeyValueSegmentIdentifier) I have thought about compatibility and performed forwards and backwards compatibility tests
• I thought about running CI.
• If I did not run CI, I ran as much locally as possible before pushing.

[shemnon]

Is there a need for full fluent API support for classic forks?

[diega]

@shemnon I think ProtocolSpecs fluency is pretty good, is that fluent API the one that you mean?

[shemnon]

APIs from this directory - https://github.com/hyperledger/besu/blob/d7e5b261141da6cbb4a8131ed2feb1603e3e68f8/evm/src/main/java/org/hyperledger/besu/evm/fluent

Guido has a fuzzer he uses there. But I'm not sure it would have caught the DIFFICULTY/RANDAO swap, even against core-geth.

[diega]

That sounds really interesting, do you know where I can find some documentation on how to run the fuzzer with Besu's EVM?

[macfarla]

this could use a changelog entry

[fab-10]

CI Publish job is failing due to a missing javadoc

> Task :evm:javadoc
/home/circleci/project/evm/src/main/java/org/hyperledger/besu/evm/ClassicEVMs.java:29: warning: no comment
public class ClassicEVMs {
       ^