[Bug?]: yarn telemetry blocks the CLI for 10 minutes in corporate networks

[DrLuke]

Self-service

• [ ] I'd be willing to implement a fix

Describe the bug

When running yarn in a locked down network, I had the issue that running yarn install would output nothing for 10 minutes and then perform the install normally. There is no indication of what errors occured in the console, and there is no verbose output available to identify the problem. After using tcpdump to see what's going on I have found the culprit: Yarn is collecting telemetry!

This needs a way shorter timeout and console output on failure, maybe with a hint on how to disable it when it fails. Also yarn desperately needs verbose output, it's frustrating how much time I've lost due to lacking error messages.

To reproduce

Run yarn install in a network that can't connect to repo.yarnpkg.com

Environment

`
$ node -v
v18.20.2

$ yarn --version
4.1.1

### Additional context

_No response_

[liuxingbaoyu]

This problem exists not only in some companies, I'm in China and I've been having to use yarn dedupe instead of yarn for the past few days because it causes more than 10s of slowness.

[arcanis]

Hmm yeah it should just be cancelled on exit - I'll take a look at that next week