Consider including mfridman/tellmewhy

[atc0005]

tellmewhy is a tool that detects a go.mod version "bump" and explains which dependency is responsible for the change.

Example from that project's README:

$ tellmewhy

Error: Go version mismatch

The required Go version has been updated to 1.21.
This change is due to an update in the module: github.com/ClickHouse/clickhouse-go/v2

Output from one of the repos I work with (I rolled back to an earlier tag before we upgraded the project to Go 1.22):

$ tellmewhy
module github.com/carlmjohnson/requests has new version: v0.23.5
go: upgraded go 1.20 => 1.22
go: added toolchain go1.22.6
go: upgraded github.com/carlmjohnson/requests v0.23.5 => v0.24.1
go: upgraded golang.org/x/net v0.24.0 => v0.28.0
go: upgraded golang.org/x/sys v0.19.0 => v0.23.0
Error: Go version mismatch

The required Go version has been updated to 1.22.
This change is due to an update in the module: github.com/carlmjohnson/requests

[atc0005]

Note to self:

Probably need a label to indicate that this is a utility and not a linter.

The README currently breaks included tooling into these categories:

• linting tools
• build tools
• testing tools

Do we need a fourth?

We currently don't have labels for all of those.

Maybe create a tools/* hiearchy?

• tools/linting
• tools/build
• tools/testing
• tools/utility
  • is this just saying a "tool" tool ?
  • maybe tools/diagnostic ?