[Yarn3] Installing temporary version of @angular/cli fails

### Command

update

### Is this a regression?

- [X] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

V16

### Description

This has happened before (https://github.com/angular/angular-cli/issues/19209) and now happens again when trying to upgrade to angular v17.


Tried to install the update with npm to check if yarn is the cause and npm goes through successfully.

### Minimal Reproduction

Try to upgrade angular 16 to 17 using yarn v3 (current specific version we're using is `v3.6.4`, but I tried to upgrade yarn to `v4.0.2` and it's the same behavior).

Global angular/cli is v17, local is v16 (obviously).

### Exception or Error

_No response_

### Your Environment

```text
Angular CLI: 16.1.6
Node: 18.14.0
Package Manager: yarn 4.0.2
OS: win32 x64

Angular: 16.1.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1601.6
@angular-devkit/build-angular 16.1.6
@angular-devkit/core 16.1.6
@angular-devkit/schematics 16.1.6
@angular/cdk 16.1.6
@angular/cli 16.1.6
@angular/material 16.1.6
@schematics/angular 16.1.6
rxjs 7.8.1
typescript 5.2.2
zone.js 0.14.2
```

### Anything else relevant?

_No response_

Start with the Angular CLI `update` command and reproduce an Angular 16-to-17 upgrade using Yarn 3 or 4, then compare the same upgrade with npm. Trace where the temporary CLI version is installed and capture the failure details; done means the Yarn-based upgrade completes successfully.

Written by the indexing model from the issue text.