Add ability to silence node install logs

First time you install pyright it dumps logs in the console that you can't seem to get rid off.

{'x86': False, 'risc': False, 'lts': False}                                                                                                                                                                                                                                        
 * Install prebuilt node (25.5.0) ../root/.local/share/uv/tools/pyright/lib/python3.13/site-packages/nodeenv.py:639: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control 
this behavior.                                                                                                                                                                                                                                                                     
  archive.extractall(src_dir, extract_list)                                                                                                                                                                                                                                        
... done. 

Since pyright only allows outputting json to the console and not a file, this means that pyright --outputjson > file.json contains broken json.

{'x86': False, 'risc': False, 'lts': False}
{
    "version": "1.1.408",
    "time": "1769610014442",
    "generalDiagnostics": [],
    "summary": {
        "filesAnalyzed": 86,
        "errorCount": 0,
        "warningCount": 0,
        "informationCount": 0,
        "timeInSec": 5.462
    }
}

Either allow us to disable all node related logs, or output to an actual json file.

Real world use case in CI pipelines:

uvx pyright --outputjson > pyright-raw-report.json

Start with the first-install path triggered by uvx pyright and the pyright --outputjson entry point; inspect how node installation output reaches stdout. Reproduce the CI command from the issue and consider the work done when the generated JSON file contains only valid JSON without node-install logs, or when those logs can be disabled.