How to reproduce:
1. Extract and open the attached "P4LocalPackage.zip" project
2. Navigate to the Version Control (Edit > Project Settings > Version Control)
3. Enable and configure settings to match for Perforce workspace
4. Press “Connect”
5. Observe the result

Expected result: The project does not take a long time to connect to VCS
Actual result: The project takes long times connecting to VCS (15-20 minutes)

Reproducible with: 2023.1.0a1, 6000.0.63f1, 6000.2.14f1, 6000.3.0f1 (820bc0c5f094), 6000.4.0a5, 6000.5.0a2

Reproduced on: Windows 11 (24H2)
Not reproduced on: No other environments tested

Notes:
- Sometimes the Unity Perforce integration does not connect and outputs: “Version Control: UpdateSettings: Timeout reading from external process”
- Projects take a very long time opening (while testing all supported streams, I noticed that each time re-opening the project took 15-20 minutes each)
- The VCS integration has enabled the "Scan Local Package On Connect" option in Version Control Settings, and projects with several local packages have a lot of files to be scanning, debugging this scenario is difficult and would be great to have a message in the logging that suggest that the "Scan Local Package On Connect" is enabled, and the project could take large time opening.