tar.gz file is not added to GitHub release during tagged build

### Checklist

- [x] I confirm there are no unresolved issues reported on the [Chocolatey Status page](https://status.chocolatey.org).
- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my problem.
- [x] I have verified this is not an issue for a specific package.
- [x] I have verified this issue is not security related.
- [x] I confirm I am using **official**, and **not** unofficial, or modified, Chocolatey products.

### What You Are Seeing?

One of the steps that is performed during a tagged build is to generate a tar.gz file that contains the Chocolatey CLI artifacts, which have been built using Mono on a Linux system, and for that file to be uploaded to the GitHub release.

This step is performed here:

https://github.com/chocolatey/choco/blob/5b5b54a6778b438ede8229097087264812bc1827/.teamcity/settings.kts#L425-L432

But it is not completing successfully, and adding the artifact has to be done manually.

### What is Expected?

The tar.gz file should be updated, without any manual intervention.

### How Did You Get This To Happen?

1. During the last couple tagged builds, the build log has been inspected and the output shows the following:

```
{"message":"Not Found","request_id":"1E0B:23EA90:F337E:108301:6733EDFD","documentation_url":"https://docs.github.com/rest"}
00:08:30 
```

### System Details

N/A

### Installed Packages

```bash
N/A
```

### Output Log

```bash
{"message":"Not Found","request_id":"1E0B:23EA90:F337E:108301:6733EDFD","documentation_url":"https://docs.github.com/rest"}
```

### Additional Context

N/A

Start with .teamcity/settings.kts at lines 425-432 and inspect the tagged-build step that uploads the tar.gz artifact. Reproduce or trace the GitHub REST response showing “Not Found”; done means the generated tar.gz is added to the GitHub release without manual intervention.

Written by the indexing model from the issue text.