fix: don't exclude fmt.Errorf

[thehowl]

... and run gofumpt on excludes.go, and update dependencies. (errcheck is failing for me, with error package "reflect" without types was imported from "github.com/gnolang/gno/gnovm/pkg/gnolang" -- I think this is due to type parameters, and updating x/tools fixes the issue).

The reason why I think we should not exclude fmt.Errorf is that, by making sure it is used, we catch wrong code like:

if err != nil {
	fmt.Errorf("invalid file: %w", err)
}

This is obviously meant to return the error, but it's not.

If the current behaviour is to be considered correct, then errors.New should also be excepted.

[kisielk]

@thehowl can you please rebase on the latest master branch? I updated the test matrix to test with more recent versions of go and dropped < 1.18 support

[thehowl]

@kisielk rebased ;)