`--curses=no` has almost no information about analysis phase

### Description of the feature request:

When specifying `--curses=no`, there's almost no information about the analysis phase (what's being downloaded, while repo rules and modexts are being executed etc.) printed.
That's a shame, as `--curses=yes` has a _lot_ of interesting info about that.

### Which category does this issue belong to?

_No response_

### What underlying problem are you trying to solve with this feature?

GitHub actions logs with `--curses=auto` behaves as `--curses=no`, which makes our CI logs not very useful when it comes to guesstimating what's going on in the analysis phase.

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

Ubuntu 22.04

### What is the output of `bazel info release`?

7.3.1

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

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

_No response_

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

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start by tracing Bazel's handling of --curses=no and --curses=auto during the analysis phase, then compare the information shown with --curses=yes. Define which analysis progress and download details should appear in CI logs, and add tests that verify the selected non-curses output.

Written by the indexing model from the issue text.