Refactoring of compare specs test & ChiadoSpecProvider

[MarekM25]

Changes

• Added ChiadoSpecProvider
• Refactored CompareSpecs

The idea was to avoid common chainspec configuration mistakes. We misconfigured maxCodeTransition for testntes many times. This PR hasn't handled Gnosis-specific Shanghai exceptions yet. This PR will give us better control on EIPs exceptions between Gnosis, Chiado <> Mainnet.

The "fun" issue founded by this test:
There is a difference in Chiado and Gnosis/Mainnet specs. Chiado enabled EIP1283 and didn't disable it. While all other networks don't enable this EIP or disable it in one of the hardforks.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• [] No

[rubo]

This requires testing and you already have the tests written. Why did you mark that section as "no" in the description? 🙂

[MarekM25]

This requires testing and you already have the tests written. Why did you mark that section as "no" in the description? 🙂

Fixed PR description ;) well it doesn't not requires testing, because the changes are only in tests classes, but indeed I wrote new tests :)