feat(forge verify-contract): --guess-constructor-args

[klkvr]

Motivation

Ref #6334

Solution

1. Added RpcOpts to VerifyArgs. If any valid eth_rpc_url is found in config and --chain is not specified, we are using explorer for chain_id from RPC. This should make UX cleaner (ref comment)
2. Added --guess-constructor-args parameter which uses Etherscan API and RPC provider to fetch creation code of contracts created directly with create transaction or directly with default CREATE2 deployer.
3. Added test for --guess-constructor-args. I wasn't able to run existing verification tests without some small updates to them (renaming --etherscan-key to --etherscan-api-key for example). Is there a chance that required env vars are not set in CI which leads to tests silently passing or I got something wrong?

The only way I can see to make --guess-constructor-args work for any contract is by implementing some kind of cast run with custom inspector which will be pretty long-running thing (some cast run's are taking several minutes on my machine). So not sure if such UX is really a best way to do it. Would be happy to get some ideas on how creation code for arbitrary contract could be fetched faster.

[mattsse]

style nit,

I'll set the env vars in CI via secrets

[klkvr]

made guess_constructor_args a separate function

also did some more testing and it seems that in some cases compile_file results in different bytecode, so changed project.compile_file to project.compile, it shouldn't take long as it compiles with the same settings, and will probably just use cache all the time

[Evalir]

nice! only one doc nit, pending vars

[onbjerg]

lgtm