fix: some verify-bytecode fixes

[klkvr]

Cleans up code a bit, removing redundant Result and preferring checking match_type.is_none() instead of keeping a separate bool.

Also removes --verification-type flag as it doesn't make much sense because user'd expect us to determine match type during comparison.

Closes #8505. The cause is etherscan bug - it returns invalid constructor arguments for mentioned contract.

I've updated logic to not rely on etherscan constructor args if --constructor-args are passed.

Also updated --constructor-args to expect multiple values and abi-encode them similarly to forge create as this seems to be the expected UX at least by the author of #8505. I've kept an option for abi-encoded args as --encoded-constructor-args

[maurelian]

Also updated --constructor-args to expect multiple values and abi-encode them similarly to forge create as this seems to be the expected UX at least by the author of #8505. I've kept an option for abi-encoded args as --encoded-constructor-args

Thanks I'm a fan of this approach.

[mattsse]

lgtm

[blmalone]

@klkvr There was a breaking change in this PR. The --json used to return a matched boolean but that's gone.

[
    {"bytecode_type":"creation","match_type":"partial"},
    {"bytecode_type":"runtime","match_type":null,"message":"Runtime code did not match - this may be due to varying compiler settings"}
]