Update Kovan chainspec

[MarekM25]

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests??

• Yes
• No

We can sync it with next smoke tests... cc: @1swaraj

[LukaszRozmej]

I don't think we want to disable those, we are here different than OE

[LukaszRozmej]

I don't think we want to disable those, we are here different than OE

[LukaszRozmej]

Ok no worries, we have proper code for handlieng OE spec:

nethermind/src/Nethermind/Nethermind.Specs/ChainSpecStyle/ChainSpecLoader.cs

Lines 163 to 167 in 2a7b759

	chainSpec.Parameters.Eip152Transition ??= GetTransitionForExpectedPricing("blake2_f", "price.blake2_f.gas_per_round", 1);
	chainSpec.Parameters.Eip1108Transition ??= GetTransitionForExpectedPricing("alt_bn128_add", "price.alt_bn128_const_operations.price", 150)
	?? GetTransitionForExpectedPricing("alt_bn128_mul", "price.alt_bn128_const_operations.price", 6000)
	?? GetTransitionForExpectedPricing("alt_bn128_pairing", "price.alt_bn128_pairing.base", 45000);
	chainSpec.Parameters.Eip2565Transition ??= GetTransitionIfInnerPathExists("modexp", "price.modexp2565");

though I like being explicit