CircleCI: fix go-lint about scalar multipliers

[syntrust]

Failed tests:

golangci-lint run -E goimports,sqlclosecheck,bodyclose,asciicheck,misspell,errorlint --timeout 5m -e "errors.As" -e "errors.Is" ./...
op-chain-ops/cmd/check-fjord/checks/checks.go:1: : # github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks
op-chain-ops/cmd/check-fjord/checks/checks.go:286:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int) (typecheck)
package checks
op-chain-ops/cmd/check-fjord/main.go:9:2: could not import github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks (-: # github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks
op-chain-ops/cmd/check-fjord/checks/checks.go:286:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int)) (typecheck)
        "github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks"
        ^
op-acceptance-tests/tests/fjord/check_scripts_test.go:11:14: could not import github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks (-: # github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks
op-chain-ops/cmd/check-fjord/checks/checks.go:286:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int)) (typecheck)
        fjordChecks "github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks"
                    ^
op-e2e/actions/proofs/fixtures.go:1: : # github.com/ethereum-optimism/optimism/op-e2e/actions/proofs [github.com/ethereum-optimism/optimism/op-e2e/actions/proofs.test]
op-e2e/actions/proofs/operator_fee_test.go:394:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int) (typecheck)
package proofs
op-e2e/actions/upgrades/dencun_fork_test.go:1: : # github.com/ethereum-optimism/optimism/op-e2e/actions/upgrades [github.com/ethereum-optimism/optimism/op-e2e/actions/upgrades.test]
op-e2e/actions/upgrades/fjord_fork_test.go:145:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int) (typecheck)
package upgrades
op-e2e/system/fjord/check_scripts_test.go:18:14: could not import github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks (-: # github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks
op-chain-ops/cmd/check-fjord/checks/checks.go:286:3: not enough arguments in call to types.NewL1CostFuncFjord
        have (*big.Int, *big.Int, *big.Int, *big.Int)
        want (*big.Int, *big.Int, *big.Int, *big.Int, *big.Int, *big.Int)) (typecheck)
        fjordChecks "github.com/ethereum-optimism/optimism/op-chain-ops/cmd/check-fjord/checks"
                    ^
make: *** [Makefile:24: lint-go] Error 1

Verified with:

golangci-lint run -E goimports,sqlclosecheck,bodyclose,asciicheck,misspell,errorlint --timeout 5m -e "errors.As" -e "errors.Is" ./...
# or 
make lint-go

[blockchaindevsh]

To minimize the diff, we can just pass 1 as the multipliers for op tests?

[syntrust]

If the multipliers are configurable, we may need to read them from the configuration. Otherwise, it is meaningless to run the check.

[blockchaindevsh]

Currently these multipliers can only be upgraded by upgrade of op-geth.

[blockchaindevsh]

The changes for check-fjord looks valid, but I'm not sure whether we're going to use the tool. If not, we can just pass 1 for the multipliers.

[syntrust]

The changes for check-fjord looks valid, but I'm not sure whether we're going to use the tool. If not, we can just pass 1 for the multipliers.

I guess that depends on our main goal—do we need to keep the tool up to date, simply pass go lint, or minimize the diff?