Unlike the package-based query (go list)
that would behave like go get underneath (#28014, #27643),
go list -m operates only with the modules already in the cache.
That makes the result stateful, often confusing.

For example,

# the module is not in our module cache yet.
$ go list -u --versions -m example.com/module
go list -m example.com/module: module "example.com/module" is not a known dependency

# package-level query.
$ go list example.com/module
go: finding example.com/module v1.0.0
go: downloading example.com/module v1.0.0
example.com/module

# now, let's run the same query.
$ go list -u --versions -m example.com/module
example.com/module v1.0.0