Tox in verbose mode?

It might be useful to have tox in more verbose mode than the default. I'm gonna explain what happened to me recently. I've prepared a CI job with fedora-python-tox. The test dependencies contain one which has to be compiled from sources and therefore needs some non-Python deps to be installed in the container in advance. If the system package is missing, pip fails to install (compile) the package, and instead of exiting with an error, it keeps trying with older and older versions of the same package all failing for the same reason. This ended up after hours because of timeout. To uncover the problem, I had to manually add
```yaml
env:
TOX_PARAMS: -vvvvv
```
to the config to see what's happening during the installation process.

I know that the verbose mode might produce a lot of logs but having a log of the installation process sounds reasonable to me. What do you think? Should this be done on the action or container image level? I believe that both can be overwritten by user settings.

Start by reviewing how the action and container handle TOX_PARAMS, then compare the default installation output with the -vvvvv behavior described in the issue. Clarify whether verbosity belongs in the action or container configuration, and consider the user override mentioned in the report. Done means the installation process provides the requested diagnostic detail without preventing user settings from overriding it.

由索引模型根据 Issue 内容生成。