azure-functions-core-tools 4.13.2 Linux x64 package references a missing CDN blob

### Version

`azure-functions-core-tools@4.13.2`

### Description

Installing the current v4 npm package on Linux x64 fails because `4.13.2` references a CDN asset that does not exist:

```text
https://cdn.functions.azure.com/public/4.0.296705/Azure.Functions.Cli.linux-x64.4.13.2.zip
```

The URL returns HTTP 404 with `BlobNotFound`. I verified the same result repeatedly from at least 2026-08-09T00:55Z through 2026-08-09T10:10Z.

This is blocking the Aspire CI job below after the repository's transient-failure automation exhausted its retries:

- Run: https://github.com/microsoft/aspire/actions/runs/31257783175
- Job: https://github.com/microsoft/aspire/actions/runs/31257783175/job/93107161164

The latest GitHub release is currently `4.12.1`, while npm resolves `@4` to `4.13.2`, which suggests the npm package may have been published before its Linux x64 asset was available.

This is the same failure class as #4501, but for the newly published `4.13.2` package and with the blob still unavailable after multiple hours.

### Steps to reproduce

On Linux x64:

```bash
npm i -g azure-functions-core-tools@4 --unsafe-perm true
```

Or probe the referenced asset directly:

```bash
curl -I https://cdn.functions.azure.com/public/4.0.296705/Azure.Functions.Cli.linux-x64.4.13.2.zip
```

### Expected behavior

The package installs successfully and the referenced CDN asset returns HTTP 200.

### Actual behavior

The installation fails because the referenced CDN URL returns HTTP 404 / `BlobNotFound`.

Start by reproducing the failure with npm i -g azure-functions-core-tools@4 --unsafe-perm true and probing the referenced CDN URL with curl. Trace how version 4.13.2 references Azure.Functions.Cli.linux-x64.4.13.2.zip and compare it with the published release assets; done means the Linux x64 asset returns HTTP 200 and the package installs successfully.

Written by the indexing model from the issue text.