In the verify UI the different process to extract contracts information from Etherscan creates several errors

[marcocastignoli]

#2238, #2232 and #2233 fail because the contract target is not specified correctly. In the verify UI we use a method based on the ContractName property, we should align it with the one in server.

E.g. The name of the contract contains spaces in the Etherscan API result, and this is simply the wrong contract name

{...
"ContractName": "yETH weighted stableswap pool",
...}

I'm proposing to move the Etherscan response parsing functionality from server to lib-sourcify and then to use the same code in server and verification UI

[kuzdogan]

Related: #2239

[marcocastignoli]

We need to release in order to publish the new version of lib-sourcify on npm. I already have a working version of verify.sourcify.dev locally that uses the local latest version of lib-sourcify.

[kuzdogan]

One thing now I realize, in #2297 we find the contract path using the Solidity parser. How does it work for Vyper to fix this issue?