Reconsider DEBUG web logs enabled by default when devtools is present

[bclozel]

In #14450, we've (re)enabled DEBUG logging for web-related classes when devtools is activated.

In light of a recent comment, we're reconsidering that. Even if the DEBUG logging experience is improved and useful in many cases, it can be overwhelming in some cases. For example, when developing an application with a lot of static resources, the console prints a lot of information.

We should maybe disable this by default, but log a message during devtools startup describing how you can get more information on the web support in logs.

[vpavic]

I've also been bothered by this while working with 2.1.0 milestones and was about to raise the same issue. The current logging levels feel too noisy and disruptive for regular local development - I would expect most users would need those logs when debugging a specific issue and not by default.

We should maybe disable this by default, but log a message during devtools startup describing how you can get more information on the web support in logs.

This sounds like a nice idea.