chore: Add abigen V2 bindings

[janjakubnanista]

Description

Recently released abigen V2 is a major improvement over the previous version. It would simplify e.g. op-deployer development workflow greatly.

Although abigen@1.15.6 binary can be installed just fine (using any distribution channel), the generated code relies on the associated code to be present in the github.com/ethereum/go-ethereum package:

// Excerpt from the generated code
import (
	"bytes"
	"errors"
	"math/big"

	"github.com/ethereum/go-ethereum/accounts/abi"
	"github.com/ethereum/go-ethereum/accounts/abi/bind/v2" // <------ THE PROBLEM
	"github.com/ethereum/go-ethereum/common"
	"github.com/ethereum/go-ethereum/core/types"
)

Since we replace github.com/ethereum/go-ethereum with github.com/ethereum-optimism/op-geth, this code is all red and squiggly.

To fix this, this PR adds additive changes from the original PR, basically:

git remote add upstream https://github.com/ethereum/go-ethereum.git
git fetch upstream
git restore --worktree --source upstream/master accounts/abi
git restore --worktree --source upstream/master cmd/abigen

The only manual changes needed were:

• flags.CheckExclusive(c, abiFlag, jsonFlag) -> utils.CheckExclusive(c, abiFlag, jsonFlag) in abigen/main.go (this commit)

[ajsutton]

I'd suggest it would be better to pull through the whole upstream release rather than cherry-picking. Otherwise we'll have a lot of conflicts to work through when we do pull through the release. We've waiting nearly 2 years for abigen v2, a little longer won't kill us. :)

[janjakubnanista]

@ajsutton okay then 😞 will try to be patient

[tynes]

We should be able to close this now