--silent is not actually silent

Brief description of your issue

This has previously implicitly been reported in #1927 by @jedieaston and explicitly in #3891 by @shalinikhare27, but unwilling to fix the problem, the developers first declared that #1927 is a feature request (since redirecting the output from stdout to log would be a new feature) and then pretended that #3891 is a duplicate, giving themselves an excuse to ignore it.

So this is explicitly not a feature request and therefore neither directly a duplicate of #1927, nor transitively by way of #3891.

I am reporting that the existing feature --silent is broken, under the expectation that the faulty implementation will be corrected to be in line with both its implicit use and user expectation.

The fact that it's broken is actually acknowledged in the documentation, which says

Runs the installer in silent mode. This suppresses all UI. The default experience shows installer progress.

A CLI is a UI. Not a GUI, usually not a TUI, but very much a UI - always and indisputably.
"This suppresses all UI" and "The default experience shows installer progress" could not both be true if this feature worked correctly.
So clearly somebody already realized that --silent isn't actually silent, and just pretended that that was a reasonable way for --silent to work.

The fact that there is no hint how to change "the default experience" is a related documentation flaw, but independent of the fact that --silent clearly and documentedly is not silent.

So. --silent is supposed to be silent by name and documented to suppress all UI.
It's not and it doesn't.

That is a flaw in the existing implementation that I am reporting, not a feature request for new functionality.

Steps to reproduce

Use --silent on any operation, look at your screen.

Expected behavior

When looking at your screen, you shouldn't see any output.
The application is silent.

Actual behavior

When looking at your screen, you will see basically all output.
The application is not silent.

Environment

Doesn't matter - universal issue for months, documented in the official documentation.

No source file or test is named. Start by reproducing the issue with --silent on any operation, then trace the CLI's handling of output and compare it with the documented promise that silent mode suppresses all UI. Done means the command produces no visible output while using --silent.