proposal: gofmt: go.mod visually split tooling and build dependencies #76127
Description
Proposal Details
Currently go.mod splits direct and indirect dependencies. My understanding is that indirect dependencies are included in binary but not directly imported. This is different from dependencies that are imported by tooling used to vet/test/scan the source code, they are conceptually different since they are not included in binary. I propose there be a third group of dependencies (grouped by a third require directive) for tooling dependencies.
Example:
tool golang.org/x/tools/cmd/stringer
require github.com/a-h/templ
require github.com/a-h/parse // indirect
require golang.org/x/text // tooling