fix: add verbosity for verification compilation error

[dutterbutter]

What :computer:

• Outputs more details on compiler related errors during verification

Why :hand:

• Previously users only saw "Verification error: Compilation error`" which was not that helpful in understanding the issue
• Now:

Verification failed:

Error:
Compilation error

Error Details:
- Invalid EVM version requested.

View verification response:
https://explorer.sepolia.era.zksync.dev/contract_verification/31422

Evidence :camera:

Include screenshots, screen recordings, or console output here demonstrating that your changes work as intended

[nbaztec]

I agree with @Karrq this is entirely new functionality that helps both EVM and zkEVM. If it's super urgent we could consider having it, but that would conflict with upstream merges that we need to take into consideration.

[dutterbutter]

@nbaztec @Karrq Can you elaborate on how this would be applicable upstream / EVM?

The contract verifier for ZKsync block explorer is specific to our implementation? The responses from the verifier (e.g. {"status":"failed","error":"Compilation error","compilationErrors":["Invalid EVM version requested."]} ) will not be the same on other block explore instances and you can't verify EVM compiled contracts with it? The changes are isolated into zksync/.

What am I missing?

[nbaztec]

Oh I was under the impression that this is a generic verification error. If it's already our custom module feel free to make any changes.

[Karrq]

Oh I was under the impression that this is a generic verification error

I had the same, considering that this previously was common with etherscan, my bad