Action stdout/stderr in bazel-out/_tmp/actions is difficult to match up with respective actions

> ATTENTION! Please read and follow:
> - if this is a _question_ about how to build / test / query / deploy using Bazel, or a _discussion starter_, send it to bazel-discuss@googlegroups.com
> - if this is a _bug_ or _feature request_, fill the form below as best as you can.

### Description of the problem / feature request:

I try to use `rules_docker` which uses `go-containerregistry`, to push a docker image to a private docker registry. I get a simple, short error: `x509: certificate signed by unknown authority`.

When I inspect the codebase of `go-containerregistry`, there is clearly a lot of logging happening.

I think there should be a way to allow this logging, and do the storing of the logs, or at least display those logs.

I tried the following without much success:
`bazel run --explain=/tmp/foobar --verbose_explanations --verbose_failures -c dbg //human/forum:image_push`

Also, inspecting the action_outs directory gave nothing:
```
Users-MacBook-Pro:d3141ad1e6fcae83ac4bb72493c727e5 kovkev$ pwd
/private/var/tmp/_bazel_kevin/d3141ad1e6fcae83ac4bb72493c727e5
Users-MacBook-Pro:d3141ad1e6fcae83ac4bb72493c727e5 kovkev$ ls -la ./execroot/__main__/bazel-out/_tmp/action_outs
total 0
drwxr-xr-x 2 kovkev wheel 64 Oct 26 23:31 .
drwxr-xr-x 3 kovkev wheel 96 Oct 26 23:31 ..
Users-MacBook-Pro:d3141ad1e6fcae83ac4bb72493c727e5 kovkev$
```

### Feature requests: what underlying problem are you trying to solve with this feature?

I think there should be a way to see the logs output. If there is, then I think it should be documented better, maybe with an example.

### What operating system are you running Bazel on?

MacOS 10.14.6

### What's the output of `bazel info release`?

release 0.29.1

### What's the output of `git remote get-url origin ; git rev-parse master ; git rev-parse HEAD` ?

Is this relevant?

### Have you found anything relevant by searching the web?

Google `bazel logging`:

https://stackoverflow.com/questions/52722448/is-there-verbose-logging-for-bazel?noredirect=1&lq=1

https://stackoverflow.com/questions/32823625/bazel-build-verbose-compiler-commands-logging

but they do not help..

Start by reproducing the report with the shown bazel run command and inspect bazel-out/_tmp/actions and action_outs. Trace how action stdout/stderr is handled, then make the relevant logs accessible or document an existing way to retrieve them; done means the output can be matched to its respective action.

Written by the indexing model from the issue text.